===Updating existing code repositories=== Wouldn't it be useful to have the ability to set a new code upload to ##non-public## as this allows us to co-work on new releases while others are still able to download previous versions. Once the new release is mature, we can set it as ##public##.\\The alternative (for co-working) is to publish updates as ##non-public## on a new (temporary) repo page and move it to the original page once it is finished but this is less user-friendly and creates unnecessary new repositories (I do know we can delete them). ===Pre-project list on the Forum=== In order to prevent users from developing code at the same time without knowing about each other (most of the time, we start with a non-public repository), it could be useful to have a ##Pre-project## list on the forum page where users can publish their intentions so other users can ask to join a project by sending a private message.\\ Currently, we could already do this on the ##Components## page by creating a new component **before** we start coding and ask for co-developers to join by placing a note with our name on the page but this is not possible for generic code.\\ A less attractive alternative would be to use the ##Questions## list but it would be hard to filter out these projects unless we **always** add a ##Pre-project## tag (by experience, I know we often forget to add Tags).\\ In some cases, we can immediately start with a public repository and ask users to join the development.