️ 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.
U
