[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff] RE: Yay! My feature is approved. Now what?
I have a different point of view. We said that the goal would be to start the ballots for committee draft in December. To achieve that, all features should be completed by December 1st. We talked about freezing the feature list to make that possible. But one day, Ryan added new proposals to the wiki without discussing them in the XLIFF TC first. Features should have been approved by the TC before adding them to the wiki. Then, the TC rushed votes for things that had not been discussed enough and approved them. And those things are still being discussed today. Work that was progressing steadily was ruined by last minute additions. We wasted months discussing a working charter and formal procedures and then threw everything down the drain. TC members had several years for proposing and documenting features for XLIFF 2.0. Suddenly, a last minute fever destroyed long debated agreements with a plethora of undiscussed changes that were blindly accepted. Considering the changes required in the schemas and specification to accommodate the new trends adopted by the TC, It might be quite difficult to vote a Committee Draft in January. In my not so humble opinion, the new proposals should have waited for XLIFF 2.1. As I said in last call, my time to leave the TC has come. I'll probably not be around to vote the specification. I have mixed feelings about this; I worked hard to see XLIFF 2.0 published as Committee Draft this year but I would vote "no" if the ballot was conducted today with current approved features. Regards, Rodolfo -- Rodolfo M. Raya email@example.com Maxprograms http://www.maxprograms.com > -----Original Message----- > From: firstname.lastname@example.org [mailto:email@example.com] On Behalf > Of Schnabel, Bryan S > Sent: Thursday, November 29, 2012 12:33 PM > To: Ryan King > Cc: firstname.lastname@example.org > Subject: [xliff] RE: Yay! My feature is approved. Now what? > > Ryan, > > No worries about "bad community citizen" behavior. I actually don't think it's > documented. I think our loose goal is to have the accepted proposals created > as Docbook files by December such that a Committee Draft takes shape in > January. > > I would not call this a hard date though - more like a goal. > > Also, I hope you don't mind, but since we never really stated this goal, I'm > cc'ing the list. > > Thanks, > > Bryan > ________________________________ > From: Ryan King [email@example.com] > Sent: Wednesday, November 28, 2012 1:40 PM > To: Schnabel, Bryan S > Subject: RE: Yay! My feature is approved. Now what? > > I'm sure it has been mentioned in calls and properly documents, but like a > bad community citizen, instead of searching for it, can you tell me what that > timeframe specifically is? > > >> But most of all, the sooner you can get your feature submitted, the better > chance we have of getting a meaningful Committee Draft in place in the > timeframe we've discussed. > > Is there a hard date? > > Thanks, > Ryan > > > > From: firstname.lastname@example.org [mailto:email@example.com] On Behalf > Of Schnabel, Bryan S > Sent: Tuesday, November 27, 2012 2:31 PM > To: firstname.lastname@example.org > Subject: [xliff] Yay! My feature is approved. Now what? > > Hi all, > > I'm encouraged that our features for XLIFF 2.0 (all but 2*) are approved and > in the queue. > > Thanks to those who worked hard to propose and pass the features! > > But the really important part comes next. You will need to transform your > good idea into a documented feature that can be merged into the working > copy of the specification. To do this you will need SVN access to the XLIFF > repository, and you will need to document your feature in a Docbook file. > > I've dashed off a quick set of instructions on how to configure your SVN client > to access the XLIFF repository. And included in this file is a template for your > Docbook entry. > > All of this (I hope) will be straightforward for you to get started. The tricky > part will be to write up your feature, compliant with the format of the rest of > the features. I spoke to Yves about all of this. He and I agree that maybe the > best way is to take a look at an existing feature to see how it's been done in > the past. > > Please feel free to request help if you get stuck. > > But most of all, the sooner you can get your feature submitted, the better > chance we have of getting a meaningful Committee Draft in place in the > timeframe we've discussed. > > Good luck, and thanks! > > Bryan > > *(and for the owners of (S4) Permission Control and > Validation<https://wiki.oasis- > open.org/xliff/XLIFF2.0/FeatureTracking#XLIFF2.0.2BAC8-Feature.2BAC8- > PermissionControl.A.28S4.29PermissionControlandValidation> and (R37) > Validations Module<https://wiki.oasis- > open.org/xliff/XLIFF2.0/FeatureTracking#XLIFF2.0.2BAC8-Feature.2BAC8- > ValidationModule.A.28R37.29ValidationsModule>, a friendly reminder to > please provide the further clarifications we discussed to the mailing list) > > Bryan Schnabel > Content Management Architect > Phone: 503.627.5282 > www.tektronix.com<http://www.tektronix.com/> > [Twitter]<http://www.tek.com/signature/twitter>[RSS]<http://www.tek.co > m/signature/rss> [Facebook] <http://www.tek.com/signature/facebook> > [Tektronix Store] <http://www.tek.com/signature/webstore> > [Tektronix Logo]