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

po 24. 3. 2025 v 22:30 odesílatel Maximillian George <
maximillian.george@gmail.com> napsal:

> Hey Melvin, thanks this is helpful. Still not sure exactly how these
> things work – where would I post a work item proposal?
>
> In other news, I've been thinking about DID documents and realised there
> is actually a MIME-type for this <https://github.com/w3c/did/issues/255>,
> so they can actually be disseminated using the ordinary NIPs for posting
> files!
>
> This opens up the door to the use case I'm interested in exploring. Now I
> just need to find the time to actually do the work...
>

I've added some more text to this, and also :
https://github.com/nostrcg/.github/blob/gh-pages/profile/WORK_ITEM_GUIDELINES.md

As an example this would be the (optional) questionnaire filled out for our
work on did-nostr

### 📌 Work Item Questionnaire

**1. Work Item Title:**
DID Nostr - Decentralized Identifiers using the Nostr Protocol

**2. Work Item Summary:**
Define a decentralized identifier (DID) method based on the Nostr protocol,
enabling decentralized identities leveraging Nostr keys and events.

**3. Relation to Nostr:**
This proposal leverages Nostr's public key infrastructure and event-based
architecture to implement Decentralized Identifiers (DIDs), enhancing
decentralized identity solutions within the Nostr ecosystem.

**4. Web & W3C Relevance:**
Aligns with W3C DID specifications and web-based decentralized identity
standards, facilitating broader interoperability and adoption across web
technologies.

**5. Type of Output:**
- Other: DID method spec
- Latest Published Version: https://nostrcg.github.io/did-nostr/

**6. Contributors:**
- Contributor 1: Melvin Carvalho
- Contributor 2: Maximillian George

**7. Source Code and Workflow:**
https://github.com/nostrcg/did-nostr
Prefer collaborative development using GitHub issues and pull requests.

**8. Additional Notes or Questions:**
Feedback from the broader community, and DID community, is welcome.


>
> Best regards,
> Max
> On 24 Mar 2025 at 07:28 +0100, Melvin Carvalho <melvincarvalho@gmail.com>,
> wrote:
>
> I've put together this optional work item questionnaire, for those that
> prefer some guidance.  This is not mandatory, but may be a useful
> exercise.  I'll link it to the README, unless I hear otherwise.
>
> 📌 Work Item Questionnaire
>
> *1. Work Item Title:* Provide a clear and descriptive title for your idea.
>
> *2. Work Item Summary:* Briefly explain your idea in simple terms. What's
> the core purpose?
>
> *3. How does this relate to Nostr?* Describe specifically how your
> proposal connects to The Nostr Protocol.
>
> *4. Web & W3C Relevance:* Explain how your proposal intersects with the
> web, existing web standards or could benefit from alignment with W3C work.
>
> *5. Type of Output:* NIP, W3C Note, Community Group Report,
> Mardown Document, Community Group Blog Post, Undecided, or more added as
> needed
>
> *6. Contributors:* Who is willing to actively contribute to developing
> this proposal? (Include yourself and ideally one or more additional
> contributors.)
>
>    -
>
>    Contributor 1:
>    -
>
>    Contributor 2 (optional):
>    -
>
>    Others (optional):
>
> *7. Source Code and Workflow:* Where will your source code live, and how
> would you prefer to collaborate?
>
> *8. Additional Notes or Questions:* Any extra context, questions, or
> ideas you'd like to share?
>
> po 17. 3. 2025 v 7:33 odesílatel Melvin Carvalho <melvincarvalho@gmail.com>
> napsal:
>
>>
>>
>> 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
>>>
>>>