Suggestion for a page with Package Ideas

[sloorush]

[Not reporting an issue but a suggestion]

Idea

A public place where people can note down and pick up ideas of packages that are needed by the community and what packages they can build.

Users

• People who want to build packages, but do not have any ideas of what might be needed by the community
• People who want a package for something but don't have the time to build one.

Implementation

• A page on the website (customisable but might lack intuitiveness)
• Pinned GitHub issue (reactions and discussions will be easier)
• GitHub discussions tab is also an excellent option (reactions and discussions are appropriately managed, and tree conversations make it kind of a list too)
• A wiki page (easier to maintain a list)

[DavinChurch]

Good idea. I like the GitHub options due to their support, but not everyone has a GitHub account so one of the other options might be more accessible.

[aplteam]

I think only the APL wiki and GitHub are practical options. Yes, one needs to have a GitHub account for this, but thanks to spammers the same is true for the APL wiki.

Using GitHub keeps it as close to the project as possible. Putting it on the APL wiki gives us more freedom.

Hmmm...

[DavinChurch]

APL Wiki can be read without an account, I'm not sure the same is true of GitHub.

[sloorush]

Github public repositories are also readable without an account. I personally feel github discussions will be a better place than the wiki because of reaction and discussion capabilities. Also that it stays close to the project.

…

On Wed, 25 Oct 2023 at 19:26, Davin Church ***@***.***> wrote: APL Wiki can be read without an account, I'm not sure the same is true of GitHub. — Reply to this email directly, view it on GitHub <#152 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AM7UPZJ2ZROA4NXSYCYTGT3YBELAPAVCNFSM6AAAAAA6PFCCB2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZZGMZTGOJVHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>