Spec-Up git governance proposal

[henkvancann]

Our enhancement proposal and git governance strategy is here: https://hackmd.io/s1TEBBluQBSL10ZT5yRVPw. The Concepts and Terminology workgroup of ToIP would love to move forward this way and we’d like to hear your opinion / questions and hopefully we can reach consensus about the way forward.
Best regards, Henk

[csuwildcat]

Why can't you just add some folks here as maintainers?

[henkvancann]

That would be great. But it's a DIF decision to grant these rights.
If I were to become (one of) the extra maintainer(s), I could keep an eye on diverging vs. matching objectives between DIF and ToIP and act accordingly in accepting PRs.

[henkvancann]

Who to contact to be added as maintainers?

I suggest https://github.com/kordwarshuis (@kordwarshuis) and myself (@henkvancann )

[csuwildcat]

Let's get in whoever wants to help

[csuwildcat]

So how would you all like to start? I am totally open to make this a collaborative project with ToIP and other contributors.

[henkvancann]

That would be awesome: a collaborative project!

If you'd add us as maintainers of the DIF repo, we could choose the consent method for our improvements to Spec-up. If you want to become a maintainer of Spec-Up-T, too, be our guest.

We have to move Spec-Up-T-related stuff from github user Blockchainbird to trustoverip; that's a just chore because I'm co-chair of the workgroup at ToIP and all members have approved our Spec-Up-T developments.

This would make life easier than what we've described here: https://hackmd.io/s1TEBBluQBSL10ZT5yRVPw#No-go-solo, which is a strict PR-based approach.

We would "bring back home" to DIF improvements that Kor Dwarshuis can explain much better. Look at the spec-up(-t) related repos at https://github.com/blockchainbird to see what we've coded.

You could indicate what you like and don't like about our developments to bring into Spec-Up or leave in Spec-Up-T. We keep that smaller set in "T" while remaining in sync with Spec-Up (DIF) as usual.
We might need to create new repos at DIF if you for example fancy the documentation site or the npm install scripts.

Suggestion:
At the start, we will report every action in the DIF Spec-Up repo upfront. Later, we could use consent: if you don't object, we move forward.

Just my two cents. I'm already a DIF member; Kor could quickly become one.

[henkvancann]

We've created the user manual: https://blockchainbird.github.io/spec-up-t-website/

[henkvancann]

Now the user manual is here: https://trustoverip.github.io/spec-up-t-website/

[talltree]

@csuwildcat On the ToIP Concepts and Terminology Working Group call today we briefly discussed this issue. Is it okay to add @henkvancann and https://github.com/kordwarshuis as maintainers?

[csuwildcat]

Yes, happy to, will do today!

…

On Mon, Nov 4, 2024, 11:56 PM Drummond Reed ***@***.***> wrote: @csuwildcat <https://github.com/csuwildcat> On the ToIP Concepts and Terminology Working Group call today we briefly discussed this issue. Is it okay to add @henkvancann <https://github.com/henkvancann> and https://github.com/kordwarshuis as maintainers? — Reply to this email directly, view it on GitHub <#65 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABAFSUEER76UF64M2RWSULZ7BFZDAVCNFSM6AAAAABJEW4BEKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJWGI4TQMJYG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[kordwarshuis]

I registered with DIF and received a signed statement back.

[csuwildcat]

Should be all set!

[kordwarshuis]

Excellent, thank you, Daniel; we'll come up with a step-by-step plan to integrate stuff with Spec-Up-T.
If you want maintainer access to the Spec-Up-T repo at TrustoverIP, we're happy to return the favor. Just let us know.

This issue can be closed.