Upcoming Requests For Comment on LIFT proposals

[John Hatton]

Dear LIFTers,

 

Following this message, I will be sending out two Requests For Comment on proposed changes to the LIFT file format.

 

Why are we taking this “RFC” approach?  Well, to be honest, we as a community haven’t really figured out how to move LIFT forward as development teams discover new requirements.   Our past has been one of people making proposals, other people misunderstanding or finding fault with them, and then the proposals dying.  In some cases, teams have simply given up and started using name spaces to encode the data they need.  While this completely informal approach has not served us, no one I’ve spoken with is keen to have a formal process, either.  So what then?  I feel that those with the most skin in the game (the development teams) do need a way to evolve LIFT. At the same time, all stakeholders need to be heard.

 

With this RFC approach, I am aiming for a proposal process which serves us well.  I have worked with the developers who want these changes to create RFCs which are somewhat more clear about what is being proposed, why they want it, and what the impact will be on existing LIFT implementations.  Note, I’m only aiming to improve the discussion, not trying to suggest who will make the final decision in all cases.  The reality is, these teams are eager to move forward with these changes, along with any modifications that they agree to during this discussion.   If you would like to discuss this overall approach or propose a different one, please use this thread to do that.

 

thanks

John Hatton
SIL Papua New Guinea, Palaso, & SIL International Software Development
Chat Google Talk: hattonjohn Skype: hattonjohn