UnfinishedProjects

When someone has answered your question, select from the dropdown: “Mark as Correct”

Also, it doesn’t hurt to give them an upvote as well ( ദ്ദി ˙ᗜ˙ )

Before you submit, hit the dropdown and select “Ask as question”.

Hmm, maybe you are right. @www-gem brought up the idea of custom tags per project I think, but you might be right that the search function should handle this well enough. For now I will plan on only predefined tags.

to reflect its current status. One thread per project. Post updates, share milestones, and discuss your work with the community. (Create a custom tag for your project, and that tag will be used for all new threads whenever talking about your project for easier search and filtering)

Edit: Deleted tag so it wouldn’t show up on the tag list.

Tips for Requesting & Giving Feedback

Note: This is not a place to post your entire projects (see “Project Showcase”)

We suggest the use of the following tags:

In-Wiki: If the item you are requesting feedback for is tied to a project or tutorial on the wiki, please use this tag in addition to one of the tags below. Our community will try to prioritize feedback for these tags, as they are contributing to our platform’s network of collaborative projects.

Brainstorming: Use this tag when you don’t actually have an “asset” to share, but instead are looking for feedback on an idea or concept that you are brainstorming.

Early-Stage: Use this tag for early stage assets. This tag lets people know that you are likely open to major changes, or “big picture” revisions. It also lets people know that this is probably not intended to look polished, but is meant to be the initial “mockups” after the brainstorming stage.

Late-Stage: This tag should be used to indicate that you are not necessarily looking for “big picture” changes, but instead are looking for feedback on ways to polish the asset. This tag is used to prevent people from trying to get you to completely change course to a new idea, when you are already committed to this path - and want to make only small to medium adjustments.

Giving Feedback:

• Remember: Each individual is at a different point in their creative journey, and their skill set & level will likely differ from your own. Try to meet the individual where they are - and provide reasonable and realistic feedback for their specific use case.
• Honest, constructive criticism: It is important to be honest and straightforward, but also ensure that your feedback is constructive. If something is wrong with it, try to offer a potential way to improve it.
• Try to give a positive with a negative: Say what you like about the asset, along with what you think could be improved.
• Be detailed: Instead of a simple statement such as “I like it, it looks great”, we should try to be constructive with our feedback. What do you like specifically - what part of it made it look good. This ensures that future renditions have a foundation of feedback to iterate off of. The individual has a better idea of what specifically is working well and what isn’t.

Clear communication and mutual respect are what help this community thrive. Thank you for being a part of this community, and helping us keep it enjoyable and rewarding for us all.

Suggestions on what to include when creating an introduction thread:

️ Only what you feel comfortable sharing:

Although this likely goes without saying, only post what information you don’t mind being public knowledge. While some individuals are more comfortable sharing Personally Identifying Information (PII), just be aware that nothing on the internet is temporary and use discretion with the information you disclose.

What brings you to our community?

Let us know what interests you about our community. If we know what you hope to get out of this community, then community members can better point you in the right direction to make the most of your time and interactions on our platforms.

• Are you here just to hang out and see what others are up to?
• Do you want to contribute to other’s projects?
• Are you hoping to submit your own project and find collaborators?
• Do you want to find other like minded individuals?
• Etc.

Share what your interests are, so people can better connect and network:

By sharing what your interests are, other members can better connect with you and reach out on certain topics. for example, if you are into 3d modeling, Game programming, and you also dabble in electronics - let us know. Others who need someone of that skill-set may want to reach out for collaboration. Also, people with the same interests may also want to network an collaborate. Let us know what you’re working on!

What are your expectations? Are you currently available to contribute, or busy with your own projects?

Are you currently looking to get involved with projects? Are you currently only expecting to hang out and chat on the forum, but are unavailable to dedicate any time to projects? Either is fine, but letting others know your current expectations can sometimes prevent future miscommunications.

Anything else you want to share!

There are numerous other things that you may feel inclined to talk about. This thread is all about you - so feel free to share whatever you want and feel comfortable with! The better the community gets to know you, the stronger our community becomes

2026-03-30:

◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤

【NodeBB 4.10.1】

◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤

╔══════════════▣◎▣══════════════╗

See nodeBB’s changelog here:

https://github.com/NodeBB/NodeBB/releases

╚══════════════▣◎▣══════════════╝

◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤

【MediaWiki 1.45.1】

◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤

╔══════════════▣◎▣══════════════╗

See MediaWiki’s changelog here:

https://www.mediawiki.org/wiki/MediaWiki_1.45

╚══════════════▣◎▣══════════════╝

️ A BRIEF SAFETY REMINDER ️

While we encourage building bridges beyond this forum, please exercise caution when moving to third-party apps. We cannot monitor or moderate external spaces.

Practice safe internet habits and never share sensitive personal information. If anyone uses this system to harass or act in bad faith, please report them to the moderators immediately so we can keep the workshop safe for everyone.

Ghosting & Stepping Back from Projects

The goal of this community is to work on open licensed projects - and when we contribute, it isn’t meant to feel like a second job. We completely understand if you want to step back from a project. . . for any reason. If you lose interest, motivation, or something unexpected comes up in your life which makes it hard for you to set time aside for your project. That’s OK! But, we do ask that you give the other team members you are working with the courtesy of informing them that you are unable to stick with your original commitments.

Sometimes it is hard to admit that we “bit off more than we could chew”, or that we are no longer interested in the project. Often we don’t want to hurt the other person’s feelings, or we are embarrassed about our change of heart - but I assure you that more often than not, the individual will not hold it against you if you are honest and let them know that you will be inactive on a project. By doing this, you are also likely preventing any burned bridges, and can come back to the project if/when you have more time and/or motivation.

Some good practices are:

1. Be honest, transparent, and upfront. Be as detailed and transparent as possible, as it makes it easier for everyone if they know what they are getting into before they commit to a project.
2. Provide examples and links. If possible, it helps when people know a bit about you, your skills, or the status of a project you are working on. If you have a portfolio, project status, etc - people will have a better idea of what they are committing to. (this isn’t a job interview - we’re all doing this in our free time, so if you have limited portfolio or experience, that is fine. Just be honest about your current state of experience, and often we all have something unique and valuable to contribute ( ◡̀_◡́)ᕤ )
3. Be thorough; put time and effort into your post. A well thought out post is going to be more likely to get interactions than a quickly thrown together one. A thoughtful and well organized post helps portray your willingness and effort towards your cause.

We suggest the use of the following tags:

Offering: Use this tag when you want to offer some help to other projects.

Include the following:

• If you have a rough estimate of your time commitment (duration, frequency, etc) - we know this is likely subject to change and fluctuation, but if you can include a general idea it will help others know what to expect.
• What you are offering. Your skills/interests - or what you specifically would like to contribute.
• Any stipulations that you might have, whether that be licensing requirements (eg. copyleft licenses only) or projects that are in a certain stage of development, etc.

Seeking: Use this tag when you are seeking help on a specific project or task.

Include the following:

• What task(s) need to be done. If you are able to narrow down your request to a specific task (or group of tasks), you are more likely to find someone willing to help. It is easier for someone to commit their time to an individual task, than it is to commit to a long term project.
• Who you are looking for. Do you need someone with a specific skill set? Do they need to have knowledge in a specific tool?

Skill-Swap: Use this tag when you would like to exchange help on each others’ project.

Include the following:

• What skill you are offering. See “Offering” tag above for examples of what to include.
• What skill are you seeking in return. See “Seeking” tag above for examples of what to include.

Team-Building: Use this tag if you are trying to put together a team for a project.

Include the following:

• What is the end goal? What is it you are trying to create. What is the vision for the team to accomplish.
• Be clear about the project size. Often, we want to accomplish something grand - but remember that it is more often better to start with a smaller goal first, then build toward the grand vision in increments.
• Have a plan. Ideas are great - but implementation takes work, so organize and prepare a plan prior to asking people to jump on board. The more time and effort you put into the initial stages will make it more likely for others to be willing to commit their valuable time to the team. Often, people want to know that they are committing to something that isn’t “half-baked”, and that you are committed and willing to put in the effort as well.
• What is your role in the project? What do you bring to the table. It’s OK if you are not an expert in anything, but people want to know that you are not simply bringing an idea to the table and expect others to build it for you. This is a team effort. Think about what you can do, and what strengths you bring to the table.
• Who are you looking for? Do you need team members with specific skill sets or experience? Maybe you just want to put together a team, and figure out what to make later - so the skill-sets don’t matter as much. . . that’s OK, but be clear about the intentions and who you are looking for to save both you and the fellow community members potentially wasted time and effort.

Clear communication and mutual respect are what help this community thrive. Thank you for being a part of this community, and helping us keep it enjoyable and rewarding for us all.

Please follow the below guidelines for each post

All Projects Showcased Need to be Openly Licensed

(open source or creative commons licenses)

Each thread inside “Project Showcase” belongs to a single project, and individuals should update the initial post with updates as they occur. This thread will be the projects home on the forum. (We ask that all projects listed here, also be added to our wiki).

Step 1 - The Title:

1. We ask that you include the abbreviated license in the title of your post for easy visibility. (we also highly suggest you add it as a tag)
2. The next part of your title should be the name of your project. If your project doesn’t have a name yet, don’t worry, this can be updated in the future.
3. Lastly, your title should include at least one overarching concept or category that it falls into. For example: “software”, or “games”.

Example Title: Please use the following format exactly for consistency across the forum, and to allow for others to search your project on the forum easier.

(AGPLv3) Amalgam [games] [software] [boardgame]

Some of the categories currently (2026/03/31) listed on the wiki:
software, world-building, handicrafts, digital-arts, audio, video, photography, games, writing, electronics
note: This is not all inclusive, but using predefined categories allows your project to be more easily searchable in the forum search

Step 2 - The Intro:

The initial part of your post should have a very brief list of the most important information:

1. Name of the project
2. License
3. Overarching topic or categories it falls into
4. Status: (active, hiatus, completed, abandoned) - this should match the thread tag
5. Links to webpage, repository, or any other primary links to the project
6. Brief description (1-2 paragraphs of what your project is about)

Step 3 - The Body:

The more detail you can provide the better. We don’t want to dictate how you organize your post, but do your best to provide as much information as you can. Sometimes this section can be trimmed down if you already have your information laid out in a wiki page, or your own website, etc.
We highly encourage that you create a wiki page to go with your post - as the real value of collaboration is achieved through the projects in the wiki in combination with forum discussion.

Some ideas for potential items to cover:

• The Vision: What is the project? What makes it unique?
• Current Progress: Is this just an idea? A half-finished prototype? Share links to your Git repo, portfolio, or screenshots if applicable.
• The “Ask”: Are you sharing your project just for the sake of sharing? Are you actively developing and interested in taking on fellow contributors? Is there something in your project you are struggling with and would like volunteer’s help with? Essentially: How can the community help you succeed?
• Expectations & Time: Your own time commitments to the project, and how you would like other community members to contribute or help with the project. If the project is in a position to take on collaborators, what are the expectations for them to get involved?
• Communication: How should people reach out, and where can people expect the majority of collaboration to take place? (Forum DMs/Chats, Signal, Matrix, Discord, etc.).

️ Project Etiquette & Reminders

• Respect the License: If you join a Libre project, respect the open nature of the work. It is important to find a balance (communication is key!) between respecting the original creator’s vision and realizing that an open license means that “forks” of a creators work may take place.
  Just remember: Our community is focused on collaboration and building connections for the greater commons. It is important to stay respectful and act in good faith. Communication and blunt honesty will prevent a lot of potential misunderstandings, but please respect the intent of the open licenses, as well as the creator’s efforts and contributions.
• Be Patient: We are all tinkering on our own time. This platform isn’t a place to find “work”, its a place for us to come together and make things that can be shared by all. Many of us have busy lives and other obligations outside of UnfinishedProjects.
• Stay Safe: Avoid sharing sensitive personal information (like your home address or phone number) in public threads.