# Project categories?

**URL:** <https://delvingbitcoin.org/t/project-categories/162>\
**Category:** Meta\
**Created:** [November 4, 2023, 11:20am UTC](https://delvingbitcoin.org/t/project-categories/162 "2023-11-04T11:20:07Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![ajtowns](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/ajtowns/32/417_2.png) [@ajtowns](https://delvingbitcoin.org/u/ajtowns)\
**Post date:** [November 4, 2023, 11:20am UTC](https://delvingbitcoin.org/t/project-categories/162/1 "2023-11-04T11:20:07Z")

</div>

What do people think about adding categories for bitcoin-related projects?

I’ve been thinking about adding one for [bitcoin-inquisition](https://github.com/bitcoin-inquisition/bitcoin/wiki) for announcements/discussions, and maybe it would be interesting for other projects that don’t want to admin their own dedicated forum?

It’s apparently possible to make a group for the project owners and give them permission to moderate posts in their category.

---

<div class="post-metadata">

**Author:** ![dgpv](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/dgpv/32/75_2.png) [@dgpv](https://delvingbitcoin.org/u/dgpv)\
**Post date:** [November 14, 2023, 10:18am UTC](https://delvingbitcoin.org/t/project-categories/162/2 "2023-11-14T10:18:04Z")

</div>

Maybe just add something like ‘tools and libraries’ category ?

---

<div class="post-metadata">

**Author:** ![dgpv](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/dgpv/32/75_2.png) [@dgpv](https://delvingbitcoin.org/u/dgpv)\
**Post date:** [November 14, 2023, 10:20am UTC](https://delvingbitcoin.org/t/project-categories/162/3 "2023-11-14T10:20:47Z")

</div>

Although with your example, bitcoin-inquisition, this might not work, as it is neither exactly a “tool” nor a “library”. But maybe you could classify it as a “tool” for a “deep investigation of the value of proposed consensus changes”

---

<div class="post-metadata">

**Author:** ![ajtowns](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/ajtowns/32/417_2.png) [@ajtowns](https://delvingbitcoin.org/u/ajtowns)\
**Post date:** [November 17, 2023, 4:48am UTC](https://delvingbitcoin.org/t/project-categories/162/4 "2023-11-17T04:48:42Z")

</div>

I like the term “working group” for a group that’s focussed on a topic, particularly if it’s probably not going to go on indefinitely, and in that vein there’s now a #wg-blockrelay group/category for discussing expanding the number of block-relay-only connections bitcoin core peers make/accept cf [#28462](https://github.com/bitcoin/bitcoin/issues/28462).

Combining a category with a group makes it possible to:

- make a private category, with posts only members of the group can see
- make a read-only category, where only group members can post, but anyone can read the posts
- make a public category, but allow group members to moderate it, rather than restricting that to the global moderators
- make it so group members automatically watch the category, so they automatically get emails notifying them about new topics/comments in the category, but not get spammed with everything else going on on the site

---

<div class="post-metadata">

**Author:** ![ajtowns](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/ajtowns/32/417_2.png) [@ajtowns](https://delvingbitcoin.org/u/ajtowns)\
**Post date:** [November 30, 2023, 8:22am UTC](https://delvingbitcoin.org/t/project-categories/162/5 "2023-11-30T08:22:42Z")

</div>

We’ve also had #wg-cluster-mempool going for a little while now; previously it was private to the group members; it’s now public, but read-only if you’re not a group member. Happy to setup variations of this for other groups, if there’s interest.

---

<div class="post-metadata">

**Author:** ![josibake](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/josibake/32/83_2.png) [@josibake](https://delvingbitcoin.org/u/josibake)\
**Post date:** [May 17, 2024, 10:32am UTC](https://delvingbitcoin.org/t/project-categories/162/6 "2024-05-17T10:32:15Z")

</div>

Was thinking `wg-silent-payments` might make sense? Currently having discussions in several different places about:

1. How to standardize indexes for light clients
2. PSBT support for sending/spending silent payment outputs
3. A silent payments descriptor

A lot of these discussions feel too early for draft BIPs/mailing list posts, hence a working group feels like a good fit?

---

<div class="post-metadata">

**Author:** ![ajtowns](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/ajtowns/32/417_2.png) [@ajtowns](https://delvingbitcoin.org/u/ajtowns)\
**Post date:** [May 17, 2024, 10:59am UTC](https://delvingbitcoin.org/t/project-categories/162/7 "2024-05-17T10:59:05Z")

</div>

(Created #wg-silent-payments after discussing offline)

---

<div class="post-metadata">

**Author:** ![harding](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/harding/32/925_2.png) [@harding](https://delvingbitcoin.org/u/harding)\
**Post date:** [May 27, 2024, 5:01pm UTC](https://delvingbitcoin.org/t/project-categories/162/8 "2024-05-27T17:01:33Z")

</div>

Is the goal for all `wg-` tags to indicate that a topic only accepts replies from allowlisted group members?

I just spent a bunch of time trying to understand a proposal tagged with a `wg-` and am frustrated that I can’t reply unless I beg someone for permission. I want to avoid wasting my time in the future, so I want to know if I should just read `wg-` tagged stuff as “Ignore this for now”.

To be clear, I appreciate the idea of small group discussions being publicly archived for posterity. Thank you to @ajtowns for setting that up and to everyone who is using that feature. I just don’t want to read stuff until I can do something with it.

---

<div class="post-metadata">

**Author:** ![ajtowns](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/ajtowns/32/417_2.png) [@ajtowns](https://delvingbitcoin.org/u/ajtowns)\
**Post date:** [May 27, 2024, 7:28pm UTC](https://delvingbitcoin.org/t/project-categories/162/9 "2024-05-27T19:28:18Z")

</div>

> [@harding](#):
>
> Is the goal for all `wg-` tags to indicate that a topic only accepts replies from allowlisted group members?

It varies per group.

> [@harding](#):
>
> I just spent a bunch of time trying to understand a proposal tagged with a `wg-` and am frustrated that I can’t reply unless I beg someone for permission.

The only group that currently has public read but not public comment/post is the silent payments working group, but as mentioned in its [“about” post](https://delvingbitcoin.org/t/about-the-wg-silent-payments-category/876), all you have to do is go to the [wg page](https://delvingbitcoin.org/g/wg-silent-payments) and click join, no begging for permission needed.

---

<div class="post-metadata">

**Author:** ![harding](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/harding/32/925_2.png) [@harding](https://delvingbitcoin.org/u/harding)\
**Post date:** [May 28, 2024, 2:53am UTC](https://delvingbitcoin.org/t/project-categories/162/10 "2024-05-28T02:53:33Z")

</div>

> [@ajtowns](#):
>
> It varies per group

Is there any way groups with different posting policies could be distinguished from each other? Maybe `cwg-` for closed working groups ? Alternatively a label like `closed` on any non-open discussions

I understand the benefits of closed working groups for developing ideas that aren’t ready for public criticism yet, especially unthoughtful criticism from entrenched opposition—but I think it’s important to label any closed discussion as such. I don’t want to see a discussion among experts and come to a mistaken belief that it represents a consensus opinion when critics didn’t have an opportunity to reply.

Additionally, I think it’s advantageous to members of a closed group to see that their posts are still protected from inline criticism from outside the group. Otherwise I worry they too may come to a mistaken belief that they have discussed an idea sufficiently enough that it represents a consensus opinion.

> [@ajtowns](#):
>
> all you have to do is go to the [wg page](https://delvingbitcoin.org/g/wg-silent-payments) and click join,

If discussion of silent payments is meant to be open, why do I need to join rather than just reply like in #wg-blockrelay or have it just be a tag like for #wg-cluster-mempool ?

---

<div class="post-metadata">

**Author:** ![josibake](https://delvingbitcoin.org/user_avatar/delvingbitcoin.org/josibake/32/83_2.png) [@josibake](https://delvingbitcoin.org/u/josibake)\
**Post date:** [May 28, 2024, 12:25pm UTC](https://delvingbitcoin.org/t/project-categories/162/11 "2024-05-28T12:25:42Z")

</div>

> [@harding](#):
>
> If discussion of silent payments is meant to be open, why do I need to join rather than just reply like in #wg-blockrelay

Creating an open group was my intention. Still figuring out how delving works, so I think this is a classic “never attribute to malice what can easily be explained by stupidity” 😅

I was under the impression for any wg you needed to join before being able to post, but if its possible to have the group where anyone can reply without joining I’d prefer that. My main reason for wanting a working group is to group different topics under the same category.
