Hi @toka, how can I join all mailing lists at the same time from the same email address via the web interface? Is there a central login to Mailman which allows me to simply click a join button to do so, or do I have to type my details every time again?
Is there any reason why we are not using the
<listname>-private, etc. pattern? I like flat namespaces, but I also like comparability. These above could possibly read similar to the pattern the W3C uses
email@example.com being migrated, read only and moderated
firstname.lastname@example.org being migrated, read only and moderated
public-global-contribwhere active partners can discuss
public-german-contribwhere the, meanwhile extended, initial group of
#14mmm(the DACH scene of alternative economies) can discuss
public-chestfor status updates and announcements, read only and moderated
public-chest-contribfor contributions to the overall process
internal-chestfor administrative conversation in the team
public-ssedasfor status updates and announcements, read only and moderated
public-ssedas-contribfor contributions from partners
Remember there are still threads on the lists. Why we don’t need separate lists for every conversation.
internal-ssedasfor administrative conversation in the team
instead. The title of a list would in a sense be self-describing its role. The goals here are
- to have as much guidance as possible about where to send specific messages once they occur.
- to keep as much conversation as possible out in the Open Web.
Meaning directly linkable and easy to join with a web browser, not neccessarily involving email (legacy and threatening Internet technology) to contribute.
- to consider mailing lists as a fallback communication channel only to be used if others (Discourse, Taiga, …) break.
I am quite worried about the
team handles, as I don’t see any benefit over Discourse’s general notification system enabled by groups like
- @Scrum https://discourse.transformap.co/groups/scrum/members
- @Team https://discourse.transformap.co/groups/team/members
- @Funding https://discourse.transformap.co/groups/funding/members
Let’s just keep in mind every organization of communication channels is also organizing the social process around, therefore impeding power structures. Else please explain to me how you want to create comparability to the circle structure and avoid uncontrolled growth in the same time. Some questions to get the conversation started:
- What is the difference between
team? Isn’t the conversation of the team about the development, thus in
- Or should all projects’ contributions feed into the same
logstream, flattening the overall organizational structure and abstracting away the projects? (Which is good in a sense!)
logcreate any advantage over the moderated public lists? Should its Discourse handle rather publish there?
I just don’t want to lose focus and create new organizational patterns which stand perpendicular to the circles/Discourse categories, scrum, the landing page’s sitemap, etc.