--> You are now talking on #web
 jensens (~jensens@194.24.158.1) has joined #web
 lucasr (~lucasr@93-97-194-210.zone5.bethere.co.uk) has joined #web
<lucasr> pcutler, ping
<pcutler> lucasr: pong
--> andreasn (~andreas@90-227-183-136-no128.tbcn.telia.com) has joined #web
<andreasn> pompidom, meeting?
--> pigeonflight (~david@72.252.224.80) has joined #web
 pigeonflight_ (~david@72.252.224.80) has joined #web
<-- pigeonflight has quit (Read error: 104 (Connection reset by peer))
--- pigeonflight_ is now known as pigeonflight
* jensens took pidgin for this irc-session and hopes it just works
<jensens> but it looks fine so far
--- bloodbare has changed the topic to: Gnome Web Meeting
<bloodbare> hi everybody
--> lincoln (~lincoln@187.1.196.150) has joined #web
* jensens waits for the countdown
--> thetet (~thet@77.118.167.152.wireless.dyn.drei.com) has joined #web
<thetet> hi...
<jensens> thetet :-)
--> csenger (~csenger@dslb-084-058-128-019.pools.arcor-ip.net) has joined #web
<csenger> hi everybody
<lucasr> ok
 meeting time
<andreasn> hi!
<lucasr> bloodbare, andreasn, csenger, jensens, lincoln, pcutler, pigeonflight, thetet, ping ;-)
<pcutler> hi
<lincoln> hi!
<jensens> greetz
<pigeonflight> Hi everyone
<csenger> :-))
<andreasn> vdepizzol said he had to run (or something like that) in order to get here in time
 so he might come around in a while
<pigeonflight> I actually thought that the meeting was to start 1 hour ago
<bloodbare> lucasr: pong
--> vdepizzol (~vinicius@201.79.242.55) has joined #web
<andreasn> oh, here he is
 hi vdepizzol 
<vdepizzol> hello there, andreasn
 :)
<thetet> hi all :)
<vdepizzol> hey everyone :)
<lucasr> shall we start?
<jensens> +1
<csenger> +1
<pcutler> +1
<bloodbare> +1
<thetet> +1
<lincoln> +1
<vdepizzol> +1
<andreasn> yeah, sure
<pigeonflight> let's go
<csenger> does somebody take minutes?
<pcutler> I will
<pigeonflight> minutes = turning on logging?
<pcutler> I'll keep a log and publish minutes as a recap
<lucasr> ok
 the agenda will cover three topics
<pcutler> I also volunteered to help lucas keep the meeting on track, so if we get off topic, I'll say something and make a note of it to discuss later in the mailing list
<lucasr> - CMS (Plone status)
 - Design
 - Release plan
<csenger> ok, let's start with the plone status
<lucasr> the questions I want some answers are
 - what's the current status of Plone implementation
 - how much effort is needed to finish it
 - honest opinion from current volunteers working on it
<csenger> we have a site that has
 - the current theme mostly working
   if we have two dedicated theme developers it would need around 4 weeks to finish it
<lucasr> csenger, what else?
<jensens> csenger: why so long?
<csenger> - the infrastructure for the frontpage (banner, feeds)
<pigeonflight> csenger: I think we'd need to itemize the tasks, so we can see the 4 weeks
<csenger> ... finished
<jensens> +1
<bloodbare> +1
<andreasn> what kind of skills are needed in order to create/implement a theme?
<pigeonflight> csenger: I'm not disagreeing with your assessmen tbtw
<csenger> pigeonflight, yes we need that.
<andreasn> just html+css or php n stuff?
<jensens> andreasn: no php. just some python
<csenger> andreasn, few python, mostly css
<jensens> csenger: what in detail is needed for front pahe whicht makes it as difficult?
<lincoln> jensens, zpt and sometimes a bit of dtml (!) =D
<pigeonflight> andreasn: skills include zpt, html, css and some Zope things (ZCML), dtml
* jensens isnt scared and cant hardly believe 4 weeks
<andreasn> sounds a bit tricky (no idea what zpt and zcml are)
<lucasr> so, the *only* thing missing is theme?
<csenger> pigeonflight, if someone knows css, the other bits are minor and we will back that up, so no dtml, no zcml
<pigeonflight> andreasn: I suspect we have those skills in abundance in this group
* vdepizzol can go with css
<csenger> lucasr, getting back to what we have:
<jensens> csenger: from my pov an experienced plone person needs not more than 4 days for the open tasks at theming level
<csenger> - the infrastructure for the different banners on the right side
* pigeonflight agrees that css is the biggy
<pcutler> test site is at:  http://gnome.rehfisch.de/
<csenger> - we have adapted the display of contenttypes to the gnome needs
<thetet> http://gnome.rehfisch.de/ looks almost finished
<lucasr> csenger, what do you mean?
<csenger> - navigation and sitemap stuff is finished (except css)
<pigeonflight> lucasr: contenttypes = things like events, news, documents etc...
<lucasr> pigeonflight, ok
 pigeonflight, how hard is to add new content types?
<pigeonflight> lucasr: adapting them would mean changing the way their data is displayed, from the default
<csenger> lucasr, making the description required for listings etc, removing it from the display, display the last author, move the references around
<thetet> do the contenttypes need more fields or just different look?
<lucasr> pigeonflight, ok
<thetet> ok
<pigeonflight> csenger: I can see how that would add up
<jensens> looks like we need a tiny schemaextender(modifier for the types. nothing difficult
<lucasr> are you documenting the implementation somewhere?
<thetet> apropos schemaextender: http://pypi.python.org/pypi/archetypes.schemaextender
<csenger> thetet, some styling, I adapted the displayed data d
 ... based on comments to some bugzilla tickets.
<pigeonflight> lucasr: should there be documentation around schemas for contenttypes and required custom views?
<thetet> ok, i see from code that schemaextender is already used
<lucasr> I think the general guideline should: never consider you'll be around all the time to maintain the website
<csenger> lucasr, other than the changelog entries .. no
 lucasr, that's right
<lucasr> so it should well documented and simple enough for a plone guy to know the state of things
<csenger> lucasr, we have added documentation to the python packages, but I have to review them
<lucasr> csenger, ok
 csenger, so, anything else on the status of plone implementation?
<jensens> lucasr: the code usally show very verbose whats happening. at least if comments and doctests (for difficult parts) are included
 lucasr: the i18n story is not complete
<pigeonflight> no trying to cause inertia, but perhaps we need a documentation sprint as part of the plans
<bloodbare> csenger: there is still the need to do a theme for PSC in order to maintain the gnome projects
 csenger: ?
<lucasr> pigeonflight, I think documentation is a hard requirement
<pigeonflight> PSC = plone software center
<lucasr> hard == essential
<csenger> bloodbare, we postponed it (murry and I), so we invested no time into it.
 lucasr, what we dont have is:
<lucasr> software center should come in a next phase
<bloodbare> csenger: ok, great to know
<csenger> - i18n (jens knows the details)
<jensens> lucasr: LinguaPlone is great, but also has its limitations.
<pigeonflight> jensens: like i18n of folders
<jensens> anyway, we can translate every template to any langauge. this may need minor work.
 pigeonflight: not a problem iirc
<bloodbare> jensens: what's the problem on LinguaPlone ?
<lucasr> the main point around translations is the format
<jensens> translating content works in LinguaPlone (short LP) by duplicating the whole content tree in the other language
<lucasr> we should use po files
<csenger> - we only have the contentsections (get involved, get started, take a tour, about). The general stuff. The rest was postponed (or maybe dropped, I did not get it exactly if things are implemented anywhere else)
 ok, i18n first
<jensens> a) With LingauPlone we should translate the whole tree always complete
<lucasr> csenger, about the sections, I guess we can review and remove what won't be done on the first moment
<bloodbare> jensens : at the begging we decided to add a /en/  ... /es/ .... / ca/ ... to the root and all the translated forlders there
<csenger> lucasr, that's what I did after talking to murray
<bloodbare> jensens: then the editors will edit the en version, an xml to po will create the po on en and import them with a po2xml
<jensens> b) partial translated content has no fallback (except we use BlueLinguaLink, half automated placeholders for non.-translated parts)
 bloodbare: but we need to build up content from the po and sync it with LP
 theres an XLIFF interface.
 so we are possible to import/export XLIFF files
<lucasr> guys, you can talk about technical details later
<bloodbare> yea
<lucasr> just want to know the general status
<jensens> lucasr: well, its essential to get an idea of the workflow
<bloodbare> jensens we can talk about that later if you want
<lucasr> jensens, true, but we can probably discuss this on mailing list
<jensens> summary: it is some work to get make it happen 
<csenger> jensens, the overview is: the internal i18n system is ready, but we have to adapt it to the gnome workflow
<lucasr> the question is: do you think it's possible to get it working on an ideal fashion?
<jensens> csenger: and partial translated content is not well supported by default
<lucasr> with po files as input and all 
 yes or no?
<jensens> lucasr: yes, but its 10-15 days work
<csenger> lucasr, with an export/import to xliff (xml translation format, jensens: correct?)
<jensens> yes
<lucasr> ok
<csenger> lucasr, the rest has to happen with xml2po (I hope for support from an xml2po developer)
<jensens> if po2xml build xliff (otherwise we need some xslt)
<bloodbare> jensens I may help with this
<lucasr> csenger, ok
 so, in summary:
<csenger> for me there are some open detail questions here
<jensens> i can work on xliff/LP integration and look at the partial-translated-content problem.
<lucasr> - 4-5 weeks to get the website in a beta state?
<csenger> stuff like the requirement for translated urls (how should that work with the po infrastructure) and other technical stuff
<lucasr> - proper gnome i18n support involves a bit more complex effort
 - css is the main area needing improvements
<jensens> csenger: at OPlone level all is LP and content.
<lucasr> - no documentation is being written
<jensens> -O
<lucasr> anything else?
<pcutler> just need to document the sub-items in that list that need work done
 (bugzilla, lgo?)
<lucasr> oh, and the infra for banners, news on front page still needs work
<jensens> technical question: is Collage used for the frontpage?
<csenger> jensens, a custom view is used with a control panel form
<bloodbare> at MainPage product there is an old frontpage that avoids using Collage ..
<jensens> csenger: hmm, we should sicuss using collage. it may reduce efforts a lot
<pigeonflight> jensens: I tend to stay away from collage
* jensens just polished trunk a lot ;)
<lucasr> guys, technical details later :-)
<jensens> aynway, it doesnt matter here
<lucasr> does my summary describe the current situation well?
<jensens> ack
<csenger> what is missing from the initial requrements is: indexing external content, let anonymous users edit copies of a page (should be droped) (a moment, have to go through my notes)
<pigeonflight> lucasr: I'd want to itemize the custom contentype views required
<lucasr> pcutler, could you add an action item for itemizing contenttype views?
<lucasr> pigeonflight, we can do this on mailing list
<pcutler> done
<pigeonflight> lucasr: no prob
<lucasr> important question: how do you see the maintenance work being done on the gnome website?
<pigeonflight> lucasr: but I'm suggesting that it be on the todo list
<csenger> ... a deployment concept (the general path is clear, but it has to be worked out with the admin team)
<bloodbare> lucasr: it's going to be hosted on redhat ?
<lucasr> bloodbare, we'll have to discuss this with sysadmin team
<pcutler> that discussion should be part of release plan (sysadmin, staging, testing)
<lucasr> how complex/hard will it be to maintain/update our plone instance?
 how often?
<lucasr> pcutler, true
<csenger> no work to publish podcasts or videos (did not see that in the requirements, but was evaluated)
<jensens> from security updates: not often (compared to php based systems)
<pcutler> csenger: we may want to revisit that, but after launch (we are brainstomring a video idea)
<lucasr> how do you think we can garantee/increase the chances we'll have a sustainable plone team in gnome?
<bloodbare> lucasr: plone needs sometimes to pack database and maybe two security updates per year
<jensens> at plone community there are some people to help. 
<csenger> lucasr, there are minor updates every three to 6 month that are backward compatible, so no action required
<lucasr> I was wondering if forming some sort of plone "official team" in the gnome community would make sense
<csenger> security updates are copied to the installation, restart the servers, that's it
<jensens> csenger: and click three time in ZMI-UI
<lucasr> create a more well-defined team with clear responsabilities
<lincoln> csenger, actually sometimes we find some problems with backward compatibilities that needs changes in code
<pcutler> lucasr: I would strongly agree
 because we will want to seprate out the plone volunteers from the content volunteers
<lucasr> would you guys be willing to be part of a team like this?
<pcutler> the advantage to using the CMS is to make it easy to get new volunteers for translations, updated content, etc
<lucasr> pcutler, yeah, I'm talking about a "plone maintainers team"
<bloodbare> lucasr: if we are enough people I think that somebody will be able when is necessary, 
<csenger> I'm with the official team.
<pigeonflight> lucasr: perhaps a team with a lifespan
<jensens> lucasr: it needs a team. i'll to help if i can (time, family, company)
<thetet> pcutler: content admin should be really easy with plone
<pigeonflight> lucasr: so 6 months and hand over
<bloodbare> lucasr: me as jensens 
<lucasr> pigeonflight, hmm, no...
<pcutler> right, that's why I think a plone team is a good idea, so we dont' confuse the two
<andreasn> pigeonflight, hand over to who?
<lucasr> I'd prefer something with the same aproach than the release team
<pigeonflight> andreasn: the next candidates for the team
<csenger> as I have written I will adminitrate and maintain the site for at least 6 month
<lucasr> if you want to leave, you have to point out someone to replace you
<csenger> but in any way we have to get a hand full of people that primary come from the gnome community to get that stable
<pigeonflight> I think there should be reasonable overlap between gnome community and plone community
<jensens> i can help with deployment. I have good experience here.
<lucasr> csenger, my plan was to bring you guys inside the gnome community
 :-)
<pigeonflight> lucasr: I'm already a gnome user
* pigeonflight also uses a mac
<csenger> lucasr, that would be great as I felt outside till today :-)
<lucasr> let me summarize my impressions
<jensens> lucasr: i'am using gnome too :) and if all rumorsa come true with 3.0 (python support etc.) ... ;)
<thetet> i'll also help if time allows
<lucasr> I'm very worried about the maintenance of a cms based website
 independently of the cms
<thetet> \me also uses gnome :)
<csenger> lucasr, but I've to much experience with life and volonteering to promise more than 6 month to a community I don't know enough
<lucasr> we have now some active plone people working on the website
 but I'd like to create conditions to garantee we'll have plone people in the long term
<jensens> to form a team a RL meeting helps usally a lot
 in Plone community we have so called sprints regulary 
<lucasr> so, it would great if you guys would be willing to form an official website maintenance team inside gnome community
<pigeonflight> like a plone guadec sprint?
<csenger> count me in for the website maintainance team.
<lucasr> csenger, cool
<jensens> i'am also at the team
<lucasr> csenger, lemme discuss this on sysadmin and board level and I'll officially propose this soon
<bloodbare> me too , as allways I'll do what my time allows me
<csenger> I'm sure we can get some more people that we know from the plone community if we have laid out plans
<lucasr> the bottomline here is: I want to create a situation where, if you realize you won't have time to work on gnome website anymore, you will have to state this clearly
<jensens> pigeonflight: wherever it is. if theres a sponsor for travel costs
<lucasr> and maybe look for someone to replace
<csenger> but I want gnome folks ;-)
<pigeonflight> I can promise a few hours per week over the next few months
<lucasr> and not just disappear :-)
<pigeonflight> jensens: regarding an in person sprint for the web site
<csenger> are there chances to get gnome people with no plone background in?
<lucasr> it's more about being around and dedicate some time when needed
<pigeonflight> jensens: ?
<lucasr> csenger, yes, probably from marketing, art and sysadmin teams
<pigeonflight> lucasr: that would work, as much of the day to day doesn't require plone specific skill
<lucasr> pcutler, action item to bring gnome people to website gang
<pcutler> csenger: I have no background, I'm from the mktg team
<jensens> pigeonflight: yes. a real world meeting, sitting together writing code, discussing, drinking beer or coke.
<csenger> that'd be great to get a mix, not just the "plone people" that do ...
<lucasr> csenger, the plone people is more needed for maintenance and extending the website with new stuff
 not for daily content management
 ok, cool
<pigeonflight> jensens: I have a good location that is willing to accomodate sprinters http://bit.ly/2BuOt
<lucasr> next topic is design
<pigeonflight> jensens: how many persons do you think we'd have on such a sprint?
<lucasr> andreasn, vdepizzol, ping ;-)
<andreasn> hellp0
<vdepizzol> so
<lucasr> pigeonflight, suggestion: discuss sprint on mailing list
<pigeonflight> no prob
<jensens> i think i cant answer all day long to another mailinglist all the time. i more like to help with solving problems in code and deployment.
<andreasn> we have started the design process and I think we're starting to reach a place where we have most of the basic ideas in place
<csenger> lucasr, pcutler short question, how many people raised the hand for the maintenance team?
<lucasr> csenger, 3 afaik
<andreasn> http://dl.getdropbox.com/u/184285/gnome.org/foundation.png
 http://dl.getdropbox.com/u/184285/gnome.org/front.png
<csenger> well, that's a start
<andreasn> http://dl.getdropbox.com/u/184285/gnome.org/a11y-test-3.png
<pcutler> yes, 3 that I saw
<andreasn> vdepizzol, paste some  mockups too
 we're still fighting about the details
<vdepizzol> at the sime time, we did different tests http://imagebin.org/index.php?mode=image&id=48704
 http://imagebin.org/index.php?mode=image&id=48705
<thetet> you can also count me in the maintainance team if another one of plone community is needed
<vdepizzol> http://imagebin.org/index.php?mode=image&id=48707
--> limi (~limi@ppp-71-139-4-200.dsl.snfc21.pacbell.net) has joined #web
<jensens> limi :-) 
<limi> hi all :)
<csenger> limi!
<lucasr> plone guys, question: what would be the best approach with the new look and feel?
 s/approach/strategy
<jensens> well, its 'just a skin'
<limi> what do you mean, implementation-wise?
<lucasr> vdepizzol, andreasn, looks great!
<limi> I thought there was a theme already
<jensens> lucasr: means, CSS and templates is not difficult to change. 
 lucasr: its just work, as in any CMS
<lucasr> mabe my question is more like: is it worth dedicating effort on the current theme when we know it will change?
<bloodbare> limi : there is a new one : http://dl.getdropbox.com/u/184285/gnome.org/front.png
<pigeonflight> any issue with outsourcing to css "slicing" service?
<limi> wow, that green makes it practically unreadable :)
<lucasr> pigeonflight, I guess if you can explain vdepizzol and andreasn how to do it, they can probably help
<csenger> no, no more work on the old theme if we want to go live with the new
<andreasn> limi, tints of green can be fixed
<thetet> it looks nice
<lucasr> ok, that's what I wanted to know
<pigeonflight> I was thinking for workflow.... design in inkscape/gimp > outsource css work > and integrate into plone
<jensens> do we want to got live with the new theme?
<thetet> but on the infrastructe (banner, rss, etc) we can still work on
<limi> once you have the HTML/CSS ready (which should be a 1-2 hour job with this design), it's easy to fit that onto Plone
<jensens> we should then separate in the concept stylke from functional parts
<lucasr> so, what would be the best strategy to sync the new design work with the plone implementation? 
<andreasn> cool, we can come up with the html/css
<vdepizzol> andreasn and me are planning also to make some subtle changes in different pages (mostly on column organizing and footer illustrations). Is this possible with plone?
<limi> yes
 just make it work in plain HTML/CSS, and we can make it work in Plone too
* limi is tired of seeing the project stalled, and would volunteer some time
<jensens> limi: do you lookat deliverance here?
<lucasr> I guess andreasn and vdepizzol need to make the design a bit more stable before writing the html/css
<limi> jensens: that's irrelevant
<csenger> I would prefere to get the css zen from the designers into the team and cooperate on skinning
<limi> but we could do that, yes
<jensens> indeed, i'am just curious ;)
<vdepizzol> lucasr: sure, we didn't have time to make the choices :)
<limi> this theme isn't very complex
<lucasr> vdepizzol, :-)

<pcutler> how does that affect the 4-5 weeks before beta? is there an estimate on timing for having the html/css?
<limi> but really, what this project needs is a strong leader to push it forward
 right now there is nobody that actually seems to own the project
 but maybe you resolved that already ;)
<thetet> lucasr?
<lucasr> limi, pcutler and I are fixing this now :-)
<limi> awesome
<csenger> and we have no pure theming person atm
<pcutler> first, we're seeking to understand where we are  :)
<limi> csenger: I could help with that, as would speedbreeze (Jonathan), I would imagine
<lucasr> do you think it makes to work on all theme-unrelated stuff while andreasn and vdepizzol finalize their design ideas?
<csenger> we have enough work to go one while the design is finished
<jensens> lucasr: we can make everything work in pure HTML w/o any CSS
<pigeonflight> I'm down for theme work
<lucasr> nice, that makes sense to me
<limi> I would prioritize getting most of the content up, and let the people that do design work with HTML/CSS until they have most of the pages ready
 the two tasks are largely independent, although some layout parts may be affected by what kind of content is there, etc
<lucasr> pcutler, action point to get someone to review the current content and clean it up
<csenger> vdepizzol, andreasn would you help with the styling based on plones markup when you finished the graphic design?
<pcutler> done, as well as the volunteers
<andreasn> csenger, sure, as long as we can learn how to do it
<lucasr> limi, that is probably related to the list of contenttype views that someone suggested here
<vdepizzol> csenger: yep
<csenger> things are either easy or plone developers will help to get things togeterh
<lucasr> I think it makes sense to have a well-defined list of contenttype views
 and then you can guys can work on it while the design is being done
<pigeonflight> andreasn: if you need initial handholding on Plone specific css issues ping me
--> bloodbare_ (~bloodbare@89.7.111.241) has joined #web
<limi> but you seem to be in good hands and have some forward energy, mail me on limi@plone.org if there are any questions I can help answer — I'll monitor the mailing list too


<lucasr> the goal on the plone side would be to have a fully working ugly website with the "final" content
<csenger> we should discuss the list of changes depending on subsections etc. on the list to get a picture of how many additional work it will be
<jensens> lucasr: perfect
<lucasr> on the design site, the goal is to deliver a html/css with the new design
<-- bloodbare_ has quit (Rooms • iPhone IRC Client • http://rooms.derflash.de)
<lucasr> then there's a collaboration phase to implement design on plone
 does that sound good for you?
<-- limi has quit (post office, see you guys later)
<pigeonflight> lucasr: sounds good
<andreasn> sounds good to me
<pigeonflight> can we have an initial roadmap/schedule on that
<jensens> lucasr: yes. it would help if the design part reduces mainly to CSS 
<pigeonflight> ?
<csenger> sounds good (that's the way to go)
<lucasr> ok, cool
<pigeonflight> a schedule, just to tie everything discussed together... 
<lucasr> andreasn, vdepizzol does that make sense for you?
--> bloodbare_ (~bloodbare@80.27.101.26) has joined #web
<vdepizzol> lucasr: yes :)
<lucasr> nice
<csenger> jensens, can you estimate the plone site of i18n?
<andreasn> yes
<csenger> s/site/side/
<lucasr> that brings us to release plan
 I want to attach our schedule to gnome one
 for those who don't know the gnome schedule: http://live.gnome.org/TwoPointTwentyseven
<jensens> csenger: integration of XLIFF  until end of may. 
<lucasr> gnome 2.28 will be released on september
 and we have several development snapshots until there
<jensens> resolving partial-translated content problem may need a new concept and research
<lucasr> I'll send a more detailed schedule proposal this week
<jensens> bloodbare_: what do you think do we need for xml2po integration in gnome translation workflow?
<lucasr> but the goal could be to have a beta version of website proposed to community on september
 what do you think?
<jensens> lucasr: sounds realistic
<pigeonflight> lucasr: makes sense
<bloodbare_> jensens, uploading generated pos on svn
<lucasr> I guess the beta design could proposed in ~4 weeks
 vdepizzol, andreasn, thoughts?
<jensens> bloodbare_: and for making xml2po work with xliff?
<bloodbare_> jensens, main content in english, generate every week po en and uploading to svn
<lucasr> pcutler, reviewed/final content could be done in the next 4-6 weeks
<csenger> we (a gnome and a plone guy/girl) should go over the initial requirements and the current needs to fix a list of tasks an prioritize them
<vdepizzol> lucasr: I was thinking if we should design as well a compatible new layout for gnome live!
<andreasn> lucasr, should we propose the design four weeks from now?
<lucasr> andreasn, yeah, something like this
<andreasn> sure, sounds sane
<vdepizzol> 4 weeks is fine
<andreasn> vdepizzol, yeah, we need to think about live.gnome.org, library.gnome.org and git.gnome.org
<pcutler> lucasr: I think 4-6 weeks for content is tight, as no one has reviewed Quim's teams work in the last year, dunno if anything needs to be changed
<andreasn> possibly bugzilla
<jensens> bloodbare_: so finish technical i18n end of june? (I'am at vacation in july)
<lucasr> pcutler, maybe there's not much to do on content
<pcutler> not for beta
<lucasr> pcutler, it might be so that we just remove stuff
<pcutler> we should be fine
<lucasr> let's see
 on plone site, what about 6-8 weeks to get a beta version of the website?
 then we'll have ~2 months to implement new design on plone
 s/site/side
<csenger> target end of june to implementation  the missing parts and have a stable base for styling 
<lucasr> what do you think?
<jensens> +1
<-- bloodbare_ has quit (Read error: 131 (Connection reset by peer))
<lucasr> I'll send a schedule proposal to mailing list along those lines then
<csenger> we also can work on a deployment starategy in parallel to the styling
<jensens> good point
<lucasr> then I'll need you to fill in with tasks
 i think we should have micro-milestones
--> bloodbare_ (~ramon@89.7.111.71) has joined #web
 bloodbare__ (~bloodbare@89.7.111.71) has joined #web
<lucasr> something like bi-weekly goals
<bloodbare__> jensens: hey sorry 
<lucasr> to make sure we know the status before we reach the deadlines
<bloodbare__> jensens: maybe we can talk about this, maybe xliff is not the best option
<jensens> lucasr:  +1 again
<lucasr> ok
<jensens> bloodbare__: its implemented
<lucasr> I think we're done
 anything else?
<pigeonflight> lucasr: +2 on micro milestoens
<csenger> who from the gnome site will work on the requirements and tasks for the next 6 weeks?
<bloodbare__> jensens: I know 
<lucasr> csenger, pcutler and I
<lucasr> I gotta go now...
<csenger> also +1 for milestones every two weeks
<pcutler> ok, thanks lucasr
* jensens needs his bed now.
<lucasr> thanks a lot everyone!
<pcutler> I will recap this, and have it out sometime tomorrow
<bloodbare__> sorry when is going to be the task list ?
 and where ?
<lucasr> that was a nice meeting
<csenger> maybe we can coordinate the plone things this week  in sorrento a bit
<lucasr> night all!
<jensens> +1 :)
<csenger> night
* pigeonflight is off to work on his other Plone projects
<jensens> csenger: see you there
--- lucasr is now known as lucasr|afk
<thetet> ciao
<vdepizzol> good night!