Re: [TOOLS-DEVELOPMENT] Making SOWs accessible to a broader pool

I agree that we want to make these "bidable" by the largest possible audience.  That said, some of them are easier to do without IETF jargon than others.  In all cases we have been including pointers to the code itself, which reall does help a potential bider understand the size of the application and where the enhancement fits.

Russ

> On Jun 26, 2019, at 4:23 PM, Alissa Cooper <alissa@cooperw.in> wrote:
> 
> I’m wondering if there are some steps we could take to write our SOWs in such a way as to make them accessible and understandable to a broader pool of potential bidders. I’ve noticed that recent ones tend to use a lot of IETF-specific jargon and acronyms without explanation and assume significant familiarity with the existing infrastructure and code base. Might it be possible to develop some boilerplate text that could be re-used across datatracker-focused RFPs that provides an introduction to the IETF, an introduction to the project, a description of the technologies in use, and links to the source code and other relevant information? 
> 
> Thanks,
> Alissa  
> _______________________________________________
> TOOLS-DEVELOPMENT mailing list
> TOOLS-DEVELOPMENT@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-development