oki, iCLA is on file now so I enabled the write access for Sabine in our Wiki.
Have fun editing :) txs and LieGrue, strub --- On Sat, 1/22/11, Mark Struberg <[email protected]> wrote: > From: Mark Struberg <[email protected]> > Subject: Re: i18n and implementation strategies > To: [email protected], [email protected] > Cc: "Sabine Winkler" <[email protected]> > Date: Saturday, January 22, 2011, 11:50 AM > Hi Sabine, Sigi! > > Sorry for not being that responsive last week, but we moved > to a new flat... > > Oki, back settled and equipped with internet again, I > looked what I can do. > > a) @Sabine: for getting you access to our wiki you need to > file a iCLA [1] (for general info see [2]) This basically > means that you have read the ALv2 and agree with it. Please > especially read section 4 of the iCLA which makes sure that > you have no company restriction from your employer which is > possibly limiting your rights to contribute. > Print it, sign it and scan it back in. Then please send the > signed iCLA to [email protected] > . Craig Russel or Sam Ruby will take care of it and once you > show up on the committers page [3] we can give you access to > our wiki. > > Sorry for this process being so verbose, but you know. In > days where Oracle sues Google and stuff happening ... ;) > > > b) Sigi, I've checked our cwiki and it seems that we don't > have a isis-admin role yet. I think it would be the best > thing to get you general confluence admin rights as well. > Chattered about that on #asfinfra. I will send a quick mail > to the IPMC asking for further clarification. > > LieGrue, > strub > > > > [1] http://www.apache.org/licenses/icla.txt > [2] http://www.apache.org/licenses > [3] http://people.apache.org/committer-index.html > > --- On Fri, 1/21/11, Sabine Winkler <[email protected]> > wrote: > > > From: Sabine Winkler <[email protected]> > > Subject: Re: i18n and implementation strategies > > To: [email protected] > > Date: Friday, January 21, 2011, 9:25 AM > > hi siegfried, > > > > thanks a lot - seems to be a "vienna connection" :-) > > > > cheers, > > sabine > > > > > > Am 21.01.2011 09:42, schrieb Siegfried Goeschl: > > > Hi Sabine, > > > > > > sorry for dropping the ball - Mark will give you > the > > edit rights today > > > (or make me to an Wiki administrator to help him) > ... > > :-) > > > > > > Cheers, > > > > > > Siegfried Goeschl > > > > > > On 1/14/11 2:39 PM, Sabine Winkler wrote: > > >> hi mark, > > >> > > >> I wrote this message last week and so I am > trying > > again now ;-) > > >> > > >> thx for response, > > >> sabine > > >> > > >> Am 05.01.2011 10:07, schrieb Sabine Winkler: > > >>> hi mark, > > >>> > > >>> I would like write some documentation on > "How > > to ... I18N" and Dan > > >>> suggested me to do so in the ISIS wiki. > > >>> While I am having an Apache account I do > not > > have any "edit" > > >>> permissions. Can you give me these > > permissions? > > >>> > > >>> thx, > > >>> sabine > > >>> > > >>> > > >>> Am 05.01.2011 08:44, schrieb Dan > Haywood: > > >>>> > > >>>> On 05/01/2011 07:17, Sabine Winkler > > wrote: > > >>>>> hi, > > >>>>> > > >>>>> happy new year! I read your > answer to > > the "I18N" question and tried > > >>>>> to get it run. nice feature! may > I ask > > some questions on this: > > >>>>> 1) I would provide a short > > documentation how to get this run - I > > >>>>> could write it as a sub-site > (like > > "Security") at a "draft". > > >>>> > > >>>> Since this should be part of the > official > > documentation, it ought to > > >>>> go into a DocBook. The one I think > it > > should live in is the "core" > > >>>> docbook that I'm currently working on > (in > > >>>> core/src/docbkx/guide/isis-core.xml > or > > something like). > > >>>> > > >>>> Two options: > > >>>> 1. edit this file then send me a > patch > > >>>> 2. write something up in the wiki, > which > > I'll then copy over to > > >>>> isis-core.xml. > > >>>> > > >>>> I think that (2) is probably easier, > and > > more immediately valuable. > > >>>> > > >>>> > > >>>>> 2) There was a small bug - the > > "normal" way is to open a bug and > > >>>>> report a fix in JIRA - correct? > > >>>> Yes. And if you have a fix, then > attach > > the patch. > > >>>> > > >>>> > > >>>>> 3) @ISIS-69 - "Get rid of some > (and > > ideally all) of the > > >>>>> FacetDecorators" - within the > last > > days I startet to get a deeper > > >>>>> understanding of the facet > decorators. > > You gave me the hint to look > > >>>>> at the TransactionXXX as an > > example/template for the > > >>>>> Test(Scenario)Reciever. As I > > understand you right this should be > > >>>>> better implemented with a > FacetFactory > > (e.q. > > >>>>> NamedAnnotationFacetFactory and > so > > on). While I am not familiar with > > >>>>> this - one stupid question - is > there > > any configuration how to > > >>>>> "register" an new factory? > > >>>> Yeah, I detailed how to register a > new > > factory in my reply on > > >>>> isis-dev; use the facets.include > > property. > > >>>> > > >>>> > > > isis.reflector.facets.include=com.mycompany.MyNamedFacetFactory > > >>>> > > >>>> You could also exclude the original > facet > > factory using the > > >>>> facets.exclude property: > > >>>> > > >>>> > > > isis.reflector.facets.exclude=org.apache.isis.core.progmodel.facets.naming.named.NamedAnnotationFacetFactory > > > > >>>> > > >>>> > > >>>> > > >>>> However, I think it probably isn't > > necessary to do this as the custom > > >>>> one explicitly included above will > > overwrite any facets installed by > > >>>> the default one. > > >>>> > > >>>> Cheers > > >>>> Dan > > >>>> > > >>>> > > >>>> > > >>>> > > >>>>> > > >>>>> > > >>>>> thanks, > > >>>>> sabine > > >>>>> > > >>> > > >>> > > >> > > >> > > > > > > > > > > >
