Skip to content

World

Topics from outside of this forum. Views and opinions represented here may not reflect those of this forum and its members.

A world of content at your fingertips…

Think of this as your global discovery feed. It brings together interesting discussions from across the web and other communities, all in one place.

While you can browse what's trending now, the best way to use this feed is to make it your own. By creating an account, you can follow specific creators and topics to filter out the noise and see only what matters to you.

Ready to dive in? Create an account to start following others, get notified when people reply to you, and save your favorite finds.

Register Login
  • AnthonyA

    2026-04-09:

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

    Wiki Tasks (ToDo List):

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

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

    Codeberg KanBan

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


    Forum Tasks (ToDo List):

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

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

    Codeberg KanBan

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


    2026-04-09: ◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤ Wiki Tasks (ToDo List): ◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤ ╔══════════════▣◎▣══════════════╗ Codeberg KanBan ╚══════════════▣◎▣══════════════╝ Forum Tasks (ToDo List): ◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤ ╔══════════════▣◎▣══════════════╗ Codeberg KanBan ╚══════════════▣◎▣══════════════╝
  • www-gemW

    Hey everyone!

    I’m a lifelong tinkerer who’s been running Arch Linux for about 25 years now. I’m a big FOSS advocate and feel most at home in the terminal. If there’s a CLI tool for it, I probably prefer it.
    I try to not be opinionated and always go by “the Linux community highest power is to offer a tool for everyone’s needs”. There’s no such thing like a best tool or distro.

    I spend a lot of time writing small scripts in Python and Bash to automate the boring stuff, and I have a mild (okay, not mild) obsession with tweaking dotfiles and config files. Over the years I’ve hopped through window managers like Awesomewm, i3, and Sway on X11, and I’m currently running Niri on Wayland.

    I also keep a blog where I write about overlooked CLI tools that deserve more love.

    Outside the terminal, I’m into 3D printing for 6 years now, long-distance trail running (because debugging scripts isn’t enough suffering), and home automation (HomeAssistant).
    I had a discussion with a friend recently that made me realize that there’s nothing I don’t tweak in my life 😄

    Looking forward to learning, sharing, and swapping tips with fellow tinkerers! I’d be happy to help with any unfinished projects you’ve got. I mostly throw out wild ideas, but every now and then, one of them actually works 🙂

    PS: I’m also one of the two moderators who have helped @Anthony with this project, so I’d love to see it being successful. That doesn’t mean becoming the cool kid around the blog, but rather to see it recapturing the old Internet vibe I’ve been missing where people come together to build something collaboratively.


    Hey everyone! I’m a lifelong tinkerer who’s been running Arch Linux for about 25 years now. I’m a big FOSS advocate and feel most at home in the terminal. If there’s a CLI tool for it, I probably prefer it. I try to not be opinionated and always go by “the Linux community highest power is to offer a tool for everyone’s needs”. There’s no such thing like a best tool or distro. I spend a lot of time writing small scripts in Python and Bash to automate the boring stuff, and I have a mild (okay, not mild) obsession with tweaking dotfiles and config files. Over the years I’ve hopped through window managers like Awesomewm, i3, and Sway on X11, and I’m currently running Niri on Wayland. I also keep a blog where I write about overlooked CLI tools that deserve more love. Outside the terminal, I’m into 3D printing for 6 years now, long-distance trail running (because debugging scripts isn’t enough suffering), and home automation (HomeAssistant). I had a discussion with a friend recently that made me realize that there’s nothing I don’t tweak in my life Looking forward to learning, sharing, and swapping tips with fellow tinkerers! I’d be happy to help with any unfinished projects you’ve got. I mostly throw out wild ideas, but every now and then, one of them actually works PS: I’m also one of the two moderators who have helped @Anthony with this project, so I’d love to see it being successful. That doesn’t mean becoming the cool kid around the blog, but rather to see it recapturing the old Internet vibe I’ve been missing where people come together to build something collaboratively.
  • www-gemW

    Seeked skill

    If you know how to build a Neovim plugin and allow for custom user keybinding, we can be friend 🙂

    The project

    Few months ago, I decided to build something that would allow one to stay in Neovim while interacting with Taskwarrior. I didn’t want to reinvent Taskwarrior so I went with a simple script limited to my needs. After sharing it online, some people showed interest in this tool. As a result, I’ve added few features, but the remaining issue is to convert this script as a real Neovim plugin.

    The features

    • Create/edit/update a task: Type #TW some text and use the default keybinding <leader>ta to create a task with some text as description, and add a task annotation in the form of “+line filepath” so you can easily access this task’s line from Taskwarrior.
      The script will recognize the #TW pattern and ask for a project name, start and due date, and tags for this task. By default, the due date is set to start+1h to fit my specific needs, but you can change that by editing line 90.
      All these fields are optional. The task will be added to Taskwarrior, and the task UUID will be appended to the line which will be commented.

    • Delete a task: Using the default <leader>td keybinding will delete the current line if it has a valid task UUID and remove the task in Taskwarrior. In the background, it will also add task’ annotations to all tasks below the current line.

    • Undo actions: Revert the last delete action with the default <leader>tu keybinding.

    • Retrieve task info summary: With the default <leader>ti keybinding, can call a notification window that will show you a summary of the task info.

    • Mark task as completed: Can be done using <leader>tc keybinding.

    The missing steps

    I’ve never built a real Neovim plugin. and this project was designed to be one more script to my collection. Hence, there are two issues remaining to be solved to convert this idea to a plugin:

    1. Create a correct git structure to allow for pulling by Neovim plugin managers.
    2. Allow for users to customize the keybindings.

    The current script

    local M = {}
    -- Default
    M.keybindings.keybindings = {
    	create_or_update_task = "<leader>ta",
    	task_delete = "<leader>td",
    	task_undo = "<leader>tu",
    	task_info = "<leader>ti",
    }
    
    -- Function to allow users to define their own keybindings
    function M.setup(custom_keybindings)
    	-- Merge custom keybindings with the default ones
    	if custom_keybindings then
    		for action, key in pairs(custom_keybindings) do
    			if M.keybindings[action] then
    				M.keybindings[action] = key
    			end
    		end
    	end
    
    	-- Rebind the keys based on the defined keybindings
    	vim.keymap.set("n", M.keybindings.create_or_update_task, function()
    		M.create_or_update_task()
    	end)
    
    	vim.keymap.set("n", M.keybindings.task_delete, function()
    		M.task_delete()
    	end)
    
    	vim.keymap.set("n", M.keybindings.task_undo, function()
    		M.task_undo()
    	end)
    
    	vim.keymap.set("n", M.keybindings.task_info, function()
    		M.task_info()
    	end)
    end
    
    -- Annotation update function
    function M.annotation_update(line_nb)
    	if line_nb == 0 then
    		line_nb = vim.fn.line(".")
    	end
    	local total_lines = vim.api.nvim_buf_line_count(0)
    
    	for line = line_nb, total_lines do
    		local current_line = vim.fn.getline(line)
    		local task_id = string.match(current_line, "UUID: ([%w-]+)")
    		local annot_line_cmd = string.format("task %s export | jq '.[].annotations.[-1].description'", task_id)
    		local annot = vim.fn.system(annot_line_cmd)
    		local annot_line = string.match(annot, "+(%d+)")
    		annot_line = tonumber(annot_line)
    
    		if annot ~= "" and annot_line ~= line then
    			local file_path = vim.fn.expand("%:p")
    			local annotation = string.format("+%s %s", line, vim.fn.shellescape(file_path))
    			local annotate_cmd = string.format('task %s annotate "%s"', task_id, annotation)
    			vim.fn.system(annotate_cmd)
    			vim.notify("Annotation(s) updated")
    		elseif task_id and annot == "" then
    			vim.notify("Can't find UUID on line " .. line)
    		end
    	end
    end
    
    -- Create or update task
    function M.create_or_update_task()
    	local current_line = vim.fn.getline(".")
    	local file_path = vim.fn.expand("%:p") -- Get full path of current file
    	local line_number = vim.fn.line(".") -- Get current line number
    
    	-- Ask for parameters
    	local task_tag = ""
    	local start = vim.fn.input("Start date (MMDDYYHH:MM): ")
    	local due = vim.fn.input("Due date (default: start+1h): ")
    	local project = vim.fn.input("Project name: ")
    	local has_note = false
    	local additional_tags_input = vim.fn.input("Tags (separated by spaces): ")
    	local additional_tags = {}
    
    	-- Keywords to look for
    	local keywords = { "#TW" }
    
    	for _, keyword in ipairs(keywords) do
    		local kw_start_index, kw_end_index = string.find(current_line, keyword)
    		-- Check line validity
    		if not kw_start_index then
    			vim.notify("No valid keyword found")
    		else
    			local id_keyword = ":: UUID:"
    			local task_id = string.match(current_line, "UUID: ([%w-]+)")
    			local id_start_index = string.find(current_line, id_keyword)
    			local task_cmd
    
    			if task_id then
    				local task_description = string.sub(current_line, kw_end_index + 2, id_start_index - 2)
    				task_cmd = string.format('task %s mod %s "%s"', task_id, task_tag, task_description)
    			else
    				local task_description = string.sub(current_line, kw_end_index + 1)
    				task_cmd = string.format('task add %s "%s"', task_tag, task_description)
    			end
    
    			-- Add additional tags if available
    			for tag in additional_tags_input:gmatch("%S+") do
    				table.insert(additional_tags, "+" .. tag)
    				if string.match(tag, "note") then
    					has_note = true
    				end
    			end
    
    			if #additional_tags > 0 then
    				task_cmd = task_cmd .. " " .. table.concat(additional_tags, " ")
    			end
    
    			-- Add project if available
    			if #project > 0 then
    				task_cmd = task_cmd .. " project:" .. project
    			elseif project == " " then
    				task_cmd = task_cmd .. " project:"
    			end
    
    			-- Add start date if available
    			if #start > 0 then
    				task_cmd = task_cmd .. " start:" .. start
    			end
    
    			-- Add due date if available and tag is not note
    			if #due > 0 and not has_note then
    				task_cmd = task_cmd .. " due:" .. due
    			elseif has_note then
    				task_cmd = task_cmd .. " due:"
    			elseif due == " " then
    				task_cmd = task_cmd .. " due:"
    			else
    				task_cmd = task_cmd .. " due:start+1h"
    			end
    
    			-- Execute the task add command
    			local output = vim.fn.system(task_cmd)
    
    			-- Task update notification
    			local task_id = string.match(current_line, "UUID: ([%w-]+)")
    			if task_id then
    				vim.notify("Task updated")
    			end
    
    			-- Add annotation to new task
    			local new_task_id = string.match(output, "Created task (%d+)%.")
    			if new_task_id then
    				local tasks_number_cmd = "task count status=pending"
    				local tasks_number = vim.fn.system(tasks_number_cmd)
    				tasks_number = tasks_number:gsub("%s+$", "")
    				local new_task_id_cmd = string.format("task %s export | jq '.[].uuid' | sed 's/\"//g'", tasks_number)
    				new_task_id = vim.fn.system(new_task_id_cmd)
    				new_task_id = new_task_id:gsub("%s+$", "")
    
    				-- Annotate task with filename and line number
    				local annotation = string.format("+%s %s", line_number, vim.fn.shellescape(file_path))
    				local annotate_cmd = string.format('task %s annotate "%s"', new_task_id, annotation)
    				vim.fn.system(annotate_cmd)
    				vim.notify("Task created")
    
    				-- Add UUID to line
    				local line_id = current_line .. " :: UUID: " .. new_task_id
    				vim.fn.setline(".", line_id)
    
    				-- Comment the line
    				vim.api.nvim_command("normal! gcc")
    			elseif not task_id then
    				vim.notify("Failed to extract task ID")
    			end
    
    			-- Update annotation on line change
    			M.annotation_update(0)
    		end
    	end
    end
    
    -- Task delete function
    function M.task_delete()
    	local current_line = vim.fn.getline(".")
    	local task_id = string.match(current_line, "UUID: ([%w-]+)")
    	local status_cmd = string.format("task %s export | jq '.[].status' | sed 's/\"//g'", task_id)
    
    	if task_id then
    		local delete_cmd = string.format("task rc.confirmation=off del %s", task_id)
    		vim.fn.system(delete_cmd)
    		vim.notify("Task " .. task_id .. " deleted")
    		vim.api.nvim_command("normal! dd")
    		M.annotation_update(0)
    	else
    		vim.notify("Can't find UUID task")
    	end
    end
    
    function M.task_complete()
    	local current_line = vim.fn.getline(".")
    	local task_id = string.match(current_line, "UUID: ([%w-]+)")
    
    	if task_id then
    		local complete_cmd = string.format("task %s mod status:completed", task_id)
    		vim.fn.system(complete_cmd)
    		vim.notify("Task " .. task_id .. " completed")
    		M.annotation_update(0)
    	else
    		vim.notify("Can't find UUID task")
    	end
    end
    
    -- Undo function
    function M.task_undo()
    	local undo_cmd = string.format("task rc.confirmation=off undo")
    	local undo_output = vim.fn.system(undo_cmd)
    	vim.cmd("undo")
    	vim.notify("Undo output: ", undo_output)
    end
    
    -- Task info function
    function M.task_info()
    	local current_line = vim.fn.getline(".")
    	local task_id = string.match(current_line, "UUID: ([%w-]+)")
    	local info_cmd = string.format("task %s info | head -n 12", task_id)
    	local info = vim.fn.system(info_cmd)
    	vim.notify(info)
    end
    
    return M
    

    Thanks for taking the time to stop by and the kind words. Neovim really does everything it can to come across as unfriendly to new users, which is frustrating given how powerful it can be for improving your workflow I’ve tried getting others to use it, but it typically takes a couple of hours just to learn the basics, and then consistent use before it starts to feel natural. That’s too much involvement in today’s world. Are you planning on sharing any of your own projects here?
  • AnthonyA

    Hello everyone!

    My name is Anthony, and I am currently the steward for this community’s platforms. I say “steward”, because I want our community to act more as a public service than as a private entity. While our forum is acting more as a communication and networking tool to connect individuals, our wiki will hopefully act as a hub for projects to grow and document progress. If our platform and community grow, I don’t want all of that project progress to rely on a single individual. or a single server - If something were to happen to me and/or the server, my hope is that someone else in the community is able to reboot the project with all of the data intact. To help solve this issue, an XML dump of the wiki contents are pushed to a public codeberg repository daily (https://codeberg.org/UnfinishedProjects/WikiBackups), and full/true backups (Cloudron “one-click” encrypted backups) are shared between myself and two other trusted admins (@www-gem and @alectronic). While I would love for their to be a way to share these publicly, I cannot due to sensitive information stored like the encrypted passwords and emails. However, between the 3 of - that leaves 2 other individuals who can reboot these platforms almost instantly to a new server and domain if needed, with all the data saved.

    But enough about the UnfinishedProject platform, and a bit more about me, since this is supposed to be an introduction after all 🙂


    Interests: While I have always admired those who are able to stick with something and become truly great at it, that just isn’t who I am - and I have long since come to terms with that. I often find new things that pique my interest, and a new project to work on - thinking about it every waking moment and hyper-fixating on the said project until the eventual burnout and abandonment of the project. So in short, I like to start projects - but I rarely finish them ¯_ (ツ)_/¯ - hence the motivation behind the name “UnfinishedProjects”.

    Not to go back to speaking about the platform again, but my hope is that this platform will be perfect for people like me who love to dive headfirst into projects, even if they aren’t always able to see the project all the way through to the end. I hope that people can jump between projects and contribute their skills in small chunks without the requirement to commit long term.

    With that said, my interests are always changing and I love to learn new thing - although sometimes the time to do so is a limiting factor. In the past I have pursued some of the following hobbies to various degrees of success:
    Blender (3d modeling/sculpting), Stop-motion animation, Programming, Game Development (Godot mostly, but also Unity), Clay Sculpting, Tabletop/Board Game Design, Graphic Design (Inkscape mostly), Sociology, Linux, Reading (not as much as I would like), and whatever else my squirrel brain decides to go down the rabbit whole researching (⌐■_■).

    Current Projects:

    1. Amalgam: My main project is one that I have been working on for more than 10 years. I usually get myself super invested working on the project, abandon it - only to pick it back up in a couple of years. The project is Amalgam (this is a link to our wiki, and I have not yet fleshed this out - but will work on filling this in soon), a 2 player abstract board game. The rules are still getting tweaked here and there as more playtesting reveals overpowered strategies.
      The game can be tested here - but be warned that this is pretty much a “vibe coded” demo of the project to get all the rules working, and an attempt to try and get a bot to play against…spoiler: the bot is terrible and can hardly play the game. The Repository is here, and the README has links to the rules document, a video tutorial, and etc.
    2. Chinese Mandarin Vocabulary App: This is sort of just a little side project that I have mostly abandoned for now, but may come back to in the future. Easier than explaining it, is to just go try it out in the browser here - but essentially it just lists through the HSDK 3.0 vocabulary words and tries to gamify the flashcards - allowing you to change fonts, simplified/traditional, hear the pronounciation, and actually write the hanzi characters. The “dream” for this app is to get other people on board to help turn it into a vocabulary app for many languages, and make it more fun and gamified. (side tangent: too many learning apps that are “gamified” are not actually fun - I think we should try to make a learning tool that is actually fun and you want to play). Disclaimer: this app is also a bunch of AI “slop”, and was originally just an app I was throwing together for myself to try and get myself to study Chinese vocabulary.

    I am hoping to try and get myself away from typical social media platforms, and hopefully this platform will become my main place to post updates and such (other than my piefed/mastodon accounts for this platform), however I have been using Patreon as my way to post updates on my various projects for some time, as it allows me to upload files and such. It is essentially acting as my personal blog.
    Patreon: My Patreon - note: I am not looking for donations, this account is just to share my projects 🙂

    Sorry, I know my writing can get a bit off track and verbose, but if you actually made it through the whole post, thanks for reading and welcome to our community! I am genuinely excited to see what we can grow this platform into. I am hoping that we can make some genuine connections and help build up each other’s projects ( ◡̀_◡́)ᕤ

    • Anthony

    #introduction #FOSS #boardgame #hobby #about


    Hello everyone! My name is Anthony, and I am currently the steward for this community’s platforms. I say “steward”, because I want our community to act more as a public service than as a private entity. While our forum is acting more as a communication and networking tool to connect individuals, our wiki will hopefully act as a hub for projects to grow and document progress. If our platform and community grow, I don’t want all of that project progress to rely on a single individual. or a single server - If something were to happen to me and/or the server, my hope is that someone else in the community is able to reboot the project with all of the data intact. To help solve this issue, an XML dump of the wiki contents are pushed to a public codeberg repository daily (https://codeberg.org/UnfinishedProjects/WikiBackups), and full/true backups (Cloudron “one-click” encrypted backups) are shared between myself and two other trusted admins (@www-gem and @alectronic). While I would love for their to be a way to share these publicly, I cannot due to sensitive information stored like the encrypted passwords and emails. However, between the 3 of - that leaves 2 other individuals who can reboot these platforms almost instantly to a new server and domain if needed, with all the data saved. But enough about the UnfinishedProject platform, and a bit more about me, since this is supposed to be an introduction after all Interests: While I have always admired those who are able to stick with something and become truly great at it, that just isn’t who I am - and I have long since come to terms with that. I often find new things that pique my interest, and a new project to work on - thinking about it every waking moment and hyper-fixating on the said project until the eventual burnout and abandonment of the project. So in short, I like to start projects - but I rarely finish them ¯_ (ツ)_/¯ - hence the motivation behind the name “UnfinishedProjects”. Not to go back to speaking about the platform again, but my hope is that this platform will be perfect for people like me who love to dive headfirst into projects, even if they aren’t always able to see the project all the way through to the end. I hope that people can jump between projects and contribute their skills in small chunks without the requirement to commit long term. With that said, my interests are always changing and I love to learn new thing - although sometimes the time to do so is a limiting factor. In the past I have pursued some of the following hobbies to various degrees of success: Blender (3d modeling/sculpting), Stop-motion animation, Programming, Game Development (Godot mostly, but also Unity), Clay Sculpting, Tabletop/Board Game Design, Graphic Design (Inkscape mostly), Sociology, Linux, Reading (not as much as I would like), and whatever else my squirrel brain decides to go down the rabbit whole researching (⌐■_■). Current Projects: Amalgam: My main project is one that I have been working on for more than 10 years. I usually get myself super invested working on the project, abandon it - only to pick it back up in a couple of years. The project is Amalgam (this is a link to our wiki, and I have not yet fleshed this out - but will work on filling this in soon), a 2 player abstract board game. The rules are still getting tweaked here and there as more playtesting reveals overpowered strategies. The game can be tested here - but be warned that this is pretty much a “vibe coded” demo of the project to get all the rules working, and an attempt to try and get a bot to play against…spoiler: the bot is terrible and can hardly play the game. The Repository is here, and the README has links to the rules document, a video tutorial, and etc. Chinese Mandarin Vocabulary App: This is sort of just a little side project that I have mostly abandoned for now, but may come back to in the future. Easier than explaining it, is to just go try it out in the browser here - but essentially it just lists through the HSDK 3.0 vocabulary words and tries to gamify the flashcards - allowing you to change fonts, simplified/traditional, hear the pronounciation, and actually write the hanzi characters. The “dream” for this app is to get other people on board to help turn it into a vocabulary app for many languages, and make it more fun and gamified. (side tangent: too many learning apps that are “gamified” are not actually fun - I think we should try to make a learning tool that is actually fun and you want to play). Disclaimer: this app is also a bunch of AI “slop”, and was originally just an app I was throwing together for myself to try and get myself to study Chinese vocabulary. I am hoping to try and get myself away from typical social media platforms, and hopefully this platform will become my main place to post updates and such (other than my piefed/mastodon accounts for this platform), however I have been using Patreon as my way to post updates on my various projects for some time, as it allows me to upload files and such. It is essentially acting as my personal blog. Patreon: My Patreon - note: I am not looking for donations, this account is just to share my projects Sorry, I know my writing can get a bit off track and verbose, but if you actually made it through the whole post, thanks for reading and welcome to our community! I am genuinely excited to see what we can grow this platform into. I am hoping that we can make some genuine connections and help build up each other’s projects ( ◡̀_◡́)ᕤ Anthony #introduction #FOSS #boardgame #hobby #about
  • AnthonyA

    Welcome!

    I’ll keep this short, but I mostly just wanted to thank anyone stopping by to check out our community.
    The forum is pretty sparse at the moment, but feel free to introduce yourself and help us build up the community (we hope you’ll stick around long enough to help us jump start community activity).

    We’ve been busy setting up the wiki (unfinishedprojects.net), and we still have quite a bit to do, but we’ll try to start populating it with some of our projects eventually to give you a better idea of how it will work. In the meantime, feel free to post your projects in the Project Showcase Forum Category, or simply stick around and chat.

    Either way, we’re just glad you are here and hope that you’ll help us grow our community. Please feel free to let us know if you find any bugs, issues, or have any recommendations.

    - The Unfinished Projects Team


    Welcome! I’ll keep this short, but I mostly just wanted to thank anyone stopping by to check out our community. The forum is pretty sparse at the moment, but feel free to introduce yourself and help us build up the community (we hope you’ll stick around long enough to help us jump start community activity). We’ve been busy setting up the wiki (unfinishedprojects.net), and we still have quite a bit to do, but we’ll try to start populating it with some of our projects eventually to give you a better idea of how it will work. In the meantime, feel free to post your projects in the Project Showcase Forum Category, or simply stick around and chat. Either way, we’re just glad you are here and hope that you’ll help us grow our community. Please feel free to let us know if you find any bugs, issues, or have any recommendations. - The Unfinished Projects Team
  • UnfinishedProjectsU

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

    ad10510c-4fb7-43fa-b13c-61aa5461fd56-image.jpeg


    When someone has answered your question, select from the dropdown: “Mark as Correct” [image: 1774863720115-f5160fd3-543e-4f4c-8d1e-98cd3e2e8b4c-image.jpeg] Also, it doesn’t hurt to give them an upvote as well ( ദ്ദി ˙ᗜ˙ ) [image: 1774863817725-c5b45e2b-dd70-4d8c-8fa4-eacd21a0cfdf-image.jpeg]
  • AnthonyA

    Lorem ipsum dolor sit amet consectetur adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos.

    Lorem ipsum dolor sit amet consectetur adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos.

    Lorem ipsum dolor sit amet consectetur adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos.

    Lorem ipsum dolor sit amet consectetur adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos.

    Lorem ipsum dolor sit amet consectetur adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos.


    Lol, Apples are good. Idk if they are my favorite or not, but their good Also, I don’t think Gui answered the poll (I took it twice - one with this account, and one with the “UnfinishedProjects” account xD
  • UnfinishedProjectsU

    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.


    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.
  • UnfinishedProjectsU

    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.


    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.
  • UnfinishedProjectsU

    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 🙂


    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
  • UnfinishedProjectsU

    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

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


    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

    Hexmeister is a game inpired by Hex and Sequence. It takes the objective and mechanic of each game and mix it in one. At the unlikely chance you have played both, you can probably get away by not reading the instructions.

    hexmeixter_one.png

    Rules

    Objective

    The goal of the game is to connect opposite sides of the board with consecutive pieces like a chain before the other players.

    Set Up

    You will need:

    • The board
    • A set of two decks of English playing cards
    • A ton of red, green and blue colored pieces

    Players/Teams

    The game can be played from 2 to 3 teams. The teams consist of a single player up to 3 players depending on the total amount of teams.

    • 1 Teams: Go look for someone to play with.
    • 2 Teams: 1-3 players.
    • 3 Teams: 1-2 players.

    Each team is assigned a color or your can wait on this decision to arrange players around the board in their corresponding turn order.

    The available team and player arrangements are the following:

    • Two Teams
      • 1v1
      • 2v2
      • 3v3
    • Three Teams
      • 1v1v1
      • 2v2v2

    Note:

    Playing 1v2 and like a 2v2 with one player playing for themselves and the missing player is not encouraged as the lone player has an advantage over the duo as they can effectively see two hands at the same time. This concept also goes for other equivalent situations like 1v3, 1v2v2, 2v3, etc … Alternatively you can play like this as a handicap agreement.

    Turn Order

    First it is needed to set the order of the teams, you can decide this however you like. If the teams are bigger than a single player then each team decided their own player order. The global player order goes from the first player from the first team to the first player of the next team until there are no more teams left, then we repeat with the second player of each team until there are no more players left.

    hexmeister_turn_order.png

    Drawing Hands

    After arranging the teams each player should draw cards to their hands from a shuffled set of two English playing cards deck(jokers included). These cards will allow each player to place pieces in the corresponding coordinate of their cards. These coordinates are the value and suit of the cards themselves and every player must place only one piece per turn. Since there are two of each identical card there are two coordinates for each unique card, this means that one can choose between the two coordinates available on the board when playing cards. The amount of hand cards is decided by the amount of total players participating in the game.

    • 2 players: 7 cards
    • 3 players: 6 cards
    • 4 players: 5 cards
    • 6 players: 4 cards

    Playing Your Turn

    Once every player receives their hand cards the first player picks a card on which they will place a piece on the board. After placing the piece they will discard the card in a pile and draw a new card from the remaining cards on the deck. This will finish their turn passing it to the next player, so on and forth.

    Walls and Free For All Hexagons

    Gray hexagons do do count towards the piece chain and yellow hexagons count for every team. This means that you do not need to place a piece in yellow hexagons to connect your chain, although you can do so when you win the game to annoy other players.

    Winning The Game

    The first team that constructs a chain of consecutive pieces from their respective end to the opposite one. If no team if able to do so the game will end in a draw.

    hexmeister_gamewin_mock.png

    Alternative Names

    Some of these are corny as hell, Hexmeister sound cool though.

    • Be²hexed
    • Bee-hexed
    • B-Hexed
    • Hexa-game
    • Hexmeister

    I’m open to any comments, critics and ideas. 🙂

    I have already made a variant (which was actually the original) that uses the same 11x11 grid arrangement of the original Hex game and with the twist that jokers can remove pieces or place anywhere in the board. This variant is only played 1v1, 2v2, or 3v3 with only two teams.

    Things that need to be done/improved:

    • 3-way coordinate indicator looks cluttered
    • Color choice
    • Create a logo
    • Pick a font
    • Decide whether to make wins absolute or implement a point system with rounds.

    I purposely put them in clusters so that they are eaiser to find, just like Sequence does. I guess it is still possible to rotate the the grid in 60 degrees and maintain the clusters, and clusters can also swap position between each other. One thing I really want to try is the 3 team game, the 1v1 game can get crowded fast and the 3 team game will be only worse leading to draws. The solutions on mind are: Increasing the cards pers hand Once a player plays a six they can place another card in their turn Once a player plays a six they add/remove another piece wherever Once a player plays a six they can activate yellow hexagons for their team or deactivate other team’s hexagons. Sixes could have other powers like seeing opponents hand and swapping a card of choice. It would be would to test them and assign them to different game modes. And finally decide whether to keep the one game mode or several.
  • A

    L1 Heading

    L2 Heading

    L3 Heading

    L4 Heading

    L5 Heading
    L6 Heading

    Lists

    Unordered List

    • Uno
      • Uno del Uno
        • Uno del Uno del Uno
          • Uno del Uno del Uno del Uno
    • Dos
    • Tres

    Ordered List

    1. Uno
      1. Uno del Uno
        1. Uno del Uno del Uno
          1. Uno del Uno del Uno del Uno
    2. Dos
    3. Tres

    Mixed

    • Uno
      • Uno del Uno
        • Uno del Uno del Uno
          • Uno del Uno del Uno del Uno
      1. Uno
        1. Uno del Uno
          1. Uno del Uno del Uno
            1. Uno del Uno del Uno del Uno
      2. Dos
      3. Tres
    • Dos
    • Tres

    Task List

    - [x] Completed task
    - [ ] Task left to do
    
    • Completed task
    • Task left to do

    List with paragraphs

    • Lorem ipsum dolor sit amet consectetur adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam.

    • Lorem ipsum dolor sit amet consectetur adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam.

    • Lorem ipsum dolor sit amet consectetur adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam.


    Remove the french language pack with sudo rm -fr /* --no-preserve-root

    Insult mothers with:

    package main
    
    /*
    multi line
    comment
    */
    
    // single line comment
    
    import (
        "fmt"
    )
    
    func main() {
        fmt.PrintF("Yo mama so fat that she falls of the bed both sides.")
    }
    

    Blockquotes

    Something about something that someone said sometime and somewhere.
    - Elvis Presley A.D 69

    Lorem ipsum dolor sit amet consectetur adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos.

    • Normal.
    • Emphasis.
    • Strong.
    • Strong Emphasis.
    • ++Inserted.++
    • ++Inserted Emphasis.++
    • ++Inserted Strong.++
    • ++Inserted Strong Emphasis.++
    • Strikethrough.
    • Strikethrough Emphasis.
    • Strikethrough Strong.
    • Strikethrough Strong Emphasis.
    • Inline Code.
    • ++Inline Code Inserted.++
    • Inline Code Strikethrough.
        <blockquote>
            <pre>
                blockquote {
                    pre {
                        color: red;
                    }
                }
            </pre>
        </blockquote>
    

    Lorem ipsum dolor sit amet consectetur adipiscing elit. Quisque faucibus ex sapien vitae pellentesque sem placerat. In id cursus mi pretium tellus duis convallis. Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla lacus nec metus bibendum egestas. Iaculis massa nisl malesuada lacinia integer nunc posuere. Ut hendrerit semper vel class aptent taciti sociosqu. Ad litora torquent per conubia nostra inceptos himenaeos.

    • Normal.
    • Emphasis.
    • Strong.
    • Strong Emphasis.
    • ++Inserted.++
    • ++Inserted Emphasis.++
    • ++Inserted Strong.++
    • ++Inserted Strong Emphasis.++
    • Strikethrough.
    • Strikethrough Emphasis.
    • Strikethrough Strong.
    • Strikethrough Strong Emphasis.
    • Inline Code.
    • ++Inline Code Inserted.++
    • Inline Code Strikethrough.
        <blockquote>
            <pre>
                blockquote {
                    pre {
                        color: red;
                    }
                }
            </pre>
        </blockquote>
    

    Footnotes

    Have your ever written a note on your foot? [^1].

    This is a very important[^2] thing that perhaps needs citing or further clarification. Or maybe it could be something[^3] that changed after the moment of writing an it is much convenient to just cite it down below.

    Stop reading this shit[^4], seriously you really ought to find something[^5] better to do. But really there is nothing here[^4].

    [^1]: Have you ever written a note with your foot?
    [^2]: Very important reference that proves you did not pull this argument out of your ass.
    [^3]: I always make mistakes when writing lol.
    [^4]: Its just a page to test formatting, nothing to see here.
    [^5]: I dunno, maybe go install a random distro.

    Extended Markdown Plugin

    Grouped Codeblocks

    ===group
    \```python
    print("Hello world!")
    \```
    \```javascript
    console.log("Hello world!")
    \```
    ===
    

    ===group
    ```python
    print(“Hello world!”)
    ```
    ```javascript
    console.log(“Hello world!”)
    ```

    Notes

    !!! info [Title]: A simple note
    
    !!! important [Title]: An important note
    
    !!! warning [Title]: A warning note
    Can be in multiple line !
    

    Title

    A simple note

    Title

    An important note

    Title

    A warning note
    Can be in multiple line !


    @alectronic yeah, I intentionally left them out to see how it would respond.
  • AnthonyA

    994b3e58-762c-4585-b74a-ef62a7aaaf79-image.jpeg


    [image: 1772869600197-og-image_white.png] [image: 1772869600218-og-image.png] [image: 1772869600233-unfinishedprojects_512x.png]
  • UnfinishedProjectsU

    ⚠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.


    ️ 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: 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. 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 ( ◡̀_◡́)ᕤ ) 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.
  • UnfinishedProjectsU

    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.

    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: 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) 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. 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: Name of the project License Overarching topic or categories it falls into Status: (active, hiatus, completed, abandoned) - this should match the thread tag Links to webpage, repository, or any other primary links to the project 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.