- Templates - nextcloud-publiccode.maadix.org

Discontinued stewardship
by Jan Ainali 11 Mar '24

11 Mar '24

Hello templates enthusiasts, As you might have seen, the Foundation for Public Code will be winding down the office in Europe (see this blog post: https://blog.publiccode.net/news/2024/02/28/changes-at-the-europe-office.ht… ) Therefore, we are sad to let you know that we will no longer be able to steward the templates project to the level which we aspire and want to be frank with you about stepping back. Johannes Dannelöf and Jan Maack Kjerby, you have been given 'owner' rights on the repository. Best regards, Jan Ainali, Codebase Steward jan(a)publiccode.net | +46762122776 | @jan_ainali | @ainali@social.coop Foundation for Public Code https://publiccode.net

4 3

Summary of January 18 call
by Jan Ainali 18 Jan '24

18 Jan '24

Hello, I'll just try to summarize the meeting for future reference. An overarching approach is that, for now, adoption is higher prioritized than completeness. We agreed that templates will be in templates directory, thus avoiding a .template extension or another way to see what belongs to the repository itself and what is the template. We'll start by using Markdown as file format, bearing in mind that it may come to change in the future. Converting from Markdown to ASCIIDoc is likely easier than the other direction. In the templates, we'll make it optional between a simpler process and one that requires GPG signing and git sign-offs. The default for now will be the simple one and the other one as an option, but with a possible change in the future as the ecosystem becomes more mature. For the repository itself, we'll go with GPG signing and git sign-offs. We'll wait with making a GitHub-template style repository until we have more experience with deployment. One point we didn't decide yet but would like to think about more, is if we want duplicated file formats, both Markdown and ASCIIDoc in order to support different repository hosting sites. (For instance, if code.eu or other Gitlab instances become more of the norm.) In general, there was an agreement to go ahead and primarily collaborate through issues and pull requests, keeping video calls as a backup for resolving matters when the bandwidth of those are too limited. -- Jan Ainali, Codebase Steward jan(a)publiccode.net | +46762122776 | @jan_ainali | @ainali@social.coop Foundation for Public Code https://publiccode.net

1 0

Location of template files
by Eric Herman 29 Nov '23

29 Nov '23

Hello all, Before adding any templates to the repository, we should agree on the location and naming. Two possible approaches include having templates reside in the root of the project alongside the repository versions or having a separate template directory. I personally favor having a directory, and thus the template files would not need to have ".template" in the names, but what do each of you feel would be best? If chat works better, feel free to share thoughts on the mattermost channel. Cheers, -Eric -- Eric Herman, Lead codebase steward Foundation for Public Code | https://publiccode.net github.com/publiccodenet | github.com/ericherman eric(a)publiccode.net | +31 620719662 | @Eric_Herman

2 1

2024

2023

Templates ----- 2024 ----- May 2024 April 2024 March 2024 February 2024 January 2024 ----- 2023 ----- December 2023 November 2023

Templates