Re: [Sat] Contributing to drafts is now easier - Core and Crash Recovery

[Rafael Belchior <[e-mail]>]

Rama,

I had to convert manually - cumbersome but not too hard. Kudos to Yaron, 
who helped me. If you use SATP-core and SATP-crash recovery as examples 
you have there most syntax you need to use. However, I would try 
Carsten's tool before doing everything manually.

Rafael

A 2024-01-23 13:29, VENKATRAMAN RAMAKRISHNA escreveu:

> Hi Rafael,
> 
> I'm catching up on this after a very long time.
> 
> These repositories look great, but is there a straightforward way for 
> me to convert a text file (either as a .txt or txt from a Word doc) to 
> markdown format so I can create a similar build structure around it? Or 
> do I need to manually create it?
> 
> IETF Datatracker allows submissions in different formats, one of which 
> is a plaintext file. That's the format I've been using thus far for the 
> SATP Use Cases draft (and the views drafts too).
> 
> Rama
> 
> From: sat <[e-mail]> On Behalf Of Rafael Belchior
> Sent: Thursday, October 26, 2023 12:15 AM
> To: [e-mail]
> Subject: [EXTERNAL] [Sat] Contributing to drafts is now easier - Core 
> and Crash Recovery
> 
> Hello Folks, I have been refactoring our SATP-Core repository to follow 
> IETF recommendations and guidelines for managing drafts in Github 
> (following i-d-template). Thanks Yaron for the help. Our build and 
> submission processes are now automated. 
> 
> ZjQcmQRYFpfptBannerStart
> 
> This Message Is From an External Sender
> 
> This message came from outside your organization.
> 
> Report Suspicious   [1]  ‌
> 
> ZjQcmQRYFpfptBannerEnd
> 
> Hello Folks,
> 
> I have been refactoring our SATP-Core repository to follow IETF 
> recommendations and guidelines for managing drafts in Github (following 
> i-d-template [2]). Thanks Yaron for the help.
> 
> Our build and submission processes are now automated. You can access 
> the latest version of the core draft (Editor's Copy) and respective 
> diff against the latest published draft (Datatracker). See more here in 
> the SATP core repo [3].
> 
> Contributing to the Core draft is much easier, since the draft is now 
> in markdown format. One can now fork the repo, make changes to the 
> draft, and submit a PR. The branch from the PR will get compiled, 
> making the assessment of changes seamless. You can check detailed 
> instructions to contribute here [4].
> 
> I encourage the authors of the other drafts to setup up their 
> repositories [5] with this method. Please let me know if you have any 
> questions or need assistance.
> 
> P.S., the latest version of the crash recovery draft is available here 
> [6].
> 
> Cheers,
> --
> -- Rafael Belchior
> 
> Ph.D. student in Computer Science and Engineering, Blockchain - Técnico
> Lisboa
> https://rafaelapb.github.io/
> https://www.linkedin.com/in/rafaelpbelchior/-

-- 
-- Rafael Belchior

Ph.D. student in Computer Science and Engineering, Blockchain - Técnico 
Lisboa
https://rafaelapb.github.io/
https://www.linkedin.com/in/rafaelpbelchior/

Links:
------
[1] 
https://us-phishalarm-ewt.proofpoint.com/EWT/v1/PjiDSg!2U-hiJRVKlMa2u_bWCEPD5UxckTFAtTKhT_I8Y-S2IKKg14YsjRymP6kCfM7BIyi-8cy_8-LfCFGKJNrz7Gj8PQ4UGDjhruqJiJdizQ$
[2] https://github.com/martinthomson/i-d-template
[3] https://github.com/ietf-satp/draft-ietf-satp-core
[4] 
https://github.com/ietf-satp/draft-ietf-satp-core/blob/main/CONTRIBUTING.md
[5] https://github.com/orgs/ietf-satp/repositories
[6] https://github.com/ietf-satp/draft-belchior-satp-gateway-recovery