Also consider using a non-personal group, this way when adding a contributor you don't have to give them access to your entire array of closes projects @richiardiandrea
@martinklepsch: I see your good point and, together with the other idea of having a boot-contrib
lib, shall I create an account called boot-contrib
where I put boot-cljs-devtools
?
@richiardiandrea: I actually thought of a single boot-contrib
project — really for simple stuff like boot-cat
, boot-gzip
, ...
boot-cljs-devtools
seems perfectly fine as an isolated project
but for things like concatenating files a full project seems overkill
yes, but we could have boot-contrib/boot-contrib
in that group right? and boot-contrib/boot-cljs-devtools
, some sort of umbrella group (maybe boot-contrib
is a bit of a misleading name)
there is already an umbrella project which is boot-clj
actually