Re: How We Can Propose and Work on Nostr CG Items

ne 9. 3. 2025 v 20:18 odesílatel Maximillian George <
maximillian.george@gmail.com> napsal:

> Hey Melvin! This looks great and allows discussion of big picture topics
> that might not fit under just one particular repo. Let’s take our DID talks
> there.
>
> I’m on my phone now but will join the group tomorrow.
>

Thanks!

I've reflected this thread here:

https://github.com/nostrcg

If any group member wishes to propose a work item.  Please feel free to
post to the list.

Alternatively, you can reach out to me privately if you have an idea, and
want some guidance!

Best
Melvin


>
> Tak soon,
> Max
> On 9 Mar 2025 at 17:42 +0100, Melvin Carvalho <melvincarvalho@gmail.com>,
> wrote:
>
> Hi everyone,
>
> I wanted to share a quick note on how we can propose and work on W3C
> Community Group (CG) work items in a simple, informal way.
> What’s a CG Work Item?
>
> A *Community Group (CG) work item* is something the group decides to work
> on together. This can be specifications, documentation, best practices, or
> other technical outputs relevant to our focus.
>
> For us, that means work items should:
>
>    - Be *related to Nostr*.
>    - Ideally *have some relevance to the web and W3C work*.
>    - Have *at least one person willing to work on it*, ideally two or
>    more.
>
> What Can We Publish?
>
> As a CG, we have the flexibility to publish a variety of outputs,
> including:
>
>    - *Specifications* – Technical documents that define standards or
>    protocols.
>    - *Schemas* – Such as a *linked data schema for Nostr*, which we’re
>    already working on.
>    - *Best practices* – Guidelines for implementing or using certain
>    technologies.
>    - *Proposals for new work* – Things like a *DID method for Nostr*,
>    which could emerge from current discussions.
>
> How Do We Handle Work Items?
>
> Right now, we have our official repo here:
>
> *https://github.com/nostrcg <https://github.com/nostrcg>*
>
> If you want to propose something new, it’s pretty simple:
>
>    1. *Share your idea* – Post it in GitHub discussions, on Nostr, or
>    anywhere people in the group will see it.
>    2. *Find interest* – If at least one person is prepared to work on it
>    (and ideally two), then great, let’s go.
>    3. *Pick a workflow* – Any item that gets interest can be moved to our
>    GitHub repo. Alternatively, if users prefer, it should also be possible to
>    work on a *Nostr-oriented workflow* like ngit.
>    4. *Iterate and discuss* – Get feedback, refine, and move forward.
>
> This keeps things flexible while making sure work items have enough
> backing to be useful.
>
> Let me know what you think! Open to any tweaks or suggestions.
>
> Cheers,
> Melvin
>
>