Workbranch

[FraGard]

No description provided.

[willu47]

• @AgnesBelt and I discussed this morning. This is trending towards the description of a CCG procedure, rather than a generally applicable guideline. I think we need both. Is it possible to split the document into a CCG procedure (e.g. Review Workflow) which could live under a separate category, on this site, or elsewhere, and the other more generally applicable content, which then links to the other guidelines on licensing?
• Another point is to add more internal links. E.g. licensing of knowledge outputs will likely be the same across briefings, journal articles, blog posts etc. and could be the subject of another guidelines. Linking to the creative commons site may not be sufficiently helpful for our audience.

[willu47]

@FraGard - a reminder to take a look at the comments above.

[FraGard]

Hi @willu47, back on it now. Based on the points also discussed by @AgnesBelt , wonder whether one could separate each post in two: 1) the general part (that will include info from our review of best practices); 2) an example from CCG: i.e. an example of workflow to be adopted for the particulat knowledge output in CCG, for it to comply with the best practices?