review
/
2022-1
2
0
Fork 0
Code Issues 3 Pull Requests Projects Releases Wiki Activity

Announce new drafts #1

New Issue
Open
opened 2022-12-02 08:45:47 -05:00 by lassik · 2 comments
lassik commented 2022-12-02 08:45:47 -05:00
Owner
Copy Link

There should be some way people can subscribe to be notified of new proposals, and new drafts of existing proposals.

Jakub suggested an RSS feed.

SRFI has a mailing list.

There should be some way people can subscribe to be notified of new proposals, and new drafts of existing proposals. Jakub suggested an RSS feed. SRFI has [a mailing list](https://srfi-email.schemers.org/srfi-announce/).
Retropikzel commented 2022-12-02 14:41:45 -05:00
Owner
Copy Link

Would it be possible to let any user join the renew organization? Then they propably woould be notifies about new repositories. It would then also be easier to post code. Or would this lead to confusing/complicated permission issues?

Would it be possible to let any user join the renew organization? Then they propably woould be notifies about new repositories. It would then also be easier to post code. Or would this lead to confusing/complicated permission issues?
lassik commented 2022-12-02 16:14:36 -05:00
Author
Owner
Copy Link

Would it be possible to let any user join the renew organization?

Yes, most likely.

SRFI has about 10 regulars (i.e. people who comment much of the time). That's not even close to the limit the software can handle.

Then they propably woould be notifies about new repositories.

GitHub now (finally!) lets people "Follow" organizations. Not sure about Gitea.

In any case, we should have whatever kinds of notifications are convenint. RSS is a good idea too. Gitea can send email notifications if we hook it up to an SMTP server.

It would then also be easier to post code. Or would this lead to confusing/complicated permission issues?

It seems Gitea lets us have multiple "Teams" per organization, with different permissions for each team.

Traditionally, we've given generous access credentials to anyone who is invested in Scheme in some way (known from mailing lists or projects, has written code, etc.) It's probably prudent to give less privileges to people who are not yet known.

> Would it be possible to let any user join the renew organization? Yes, most likely. SRFI has about 10 regulars (i.e. people who comment much of the time). That's not even close to the limit the software can handle. > Then they propably woould be notifies about new repositories. GitHub now (finally!) lets people "Follow" organizations. Not sure about Gitea. In any case, we should have whatever kinds of notifications are convenint. RSS is a good idea too. Gitea can send email notifications if we hook it up to an SMTP server. > It would then also be easier to post code. Or would this lead to confusing/complicated permission issues? It seems Gitea lets us have multiple "Teams" per organization, with different permissions for each team. Traditionally, we've given generous access credentials to anyone who is invested in Scheme in some way (known from mailing lists or projects, has written code, etc.) It's probably prudent to give less privileges to people who are not yet known.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
draft-1
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: review/2022-1#1
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?