As others might wonder about knowledge requirements I thought I'd follow up here too.
Currently, there is only one rule about the go-formal organisation: no private members. This doesn't require "formal" knowledge as is. The idea when go-formal started was to provide a place people could put work related to formal verification in and for go. There is no other agenda, and so the overhead of maintaining it is quite minimal. However, I would expect a minimal requirement would be to act as a proponent for housing formal tech in and for Go. Doing so doesn't necessary imply being a formal tech expert. It might even help to not be an expert so as to avoid bias in inclusion. On the other hand, of course if someone with impressive credentials put their name on it that would help too. Scott On Wednesday, 23 January 2019 13:59:59 UTC+1, Marko Ristin wrote: > > (Pardon, please ignore the previous message, it should have been private.) > > Le mer. 23 janv. 2019 à 13:58, Marko Ristin-Kaufmann <marko....@gmail.com > <javascript:>> a écrit : > >> Hi Scott, >> Could you describe a bit in more detail what needs to be done and how >> often? Are there any knowledge requirements? >> >> I already develop github.com/Parquery/gocontracts and I am quite >> interested in the topic so I might be a potential candidate. >> >> Cheers Marko >> >> Le mer. 23 janv. 2019 à 10:20, Scott Cotton <w...@iri-labs.com >> <javascript:>> a écrit : >> >>> Hello Gophers, >>> >>> Some time ago, I started the go-formal github organisation as a place >>> for formal analysis tools in and for Go. >>> >>> I am looking for a volunteer to take over ownership of the github >>> organisation go-formal as I will be unable to that role starting >>> in the coming weeks. >>> >>> The administrative overhead of this role is so far quite minimal while I >>> think it's a very good thing to have a place for such tools >>> in Go. >>> >>> As a reminder to those who might be wondering "formal analysis tools" is >>> somewhat open ended in scope but to the current maintainer refers to tools >>> the likes of which can be found in many conference tool papers such as CAV, >>> FMCAD, POPL, etc, as well as many other languages (CBMC, ...) which >>> involve formal logic. >>> >>> Some ideas came to mind for folks who might be interested in becoming >>> the github go-formal owner (in no particular order): >>> 1. Alan Donavan of the golang analysis packages. >>> 2. GopherSat authors. >>> 3. Others who have worked on formal projects in Go but less visibly. >>> 4. go-critic and staticcheck.io authors. >>> >>> Please do feel free to contact me off-line or here on go-nuts for >>> details. >>> >>> Best, >>> Scott >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "golang-nuts" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to golang-nuts...@googlegroups.com <javascript:>. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
