OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: 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 [ryanki@microsoft.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: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Schnabel, Bryan S
Sent: Tuesday, November 27, 2012 2:31 PM
To: xliff@lists.oasis-open.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.com/signature/rss> [Facebook] <http://www.tek.com/signature/facebook>  [Tektronix Store] <http://www.tek.com/signature/webstore>
[Tektronix Logo]

GIF image

GIF image

GIF image

GIF image

GIF image



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]