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
