How to organize an EFSPACM project

First thing, it's best to be in our facebook group, https://www.facebook.com/groups/680430459199270 - after some time you probably are going to feel the atmosphere, and perhaps you will not only want to take part in projects, but to organize one yourself. Although it's lots of fun and gives a lot of satisfaction, it also requires lots of work and responsibility.

Neal D Retke: I think the organizational aspect should be determined by the person creating the event. Different things work better for different people, and one's technique may be unsuitable for another - I think if a project is unclear or fails to get off the ground ( which I've had happen here ) it should be up to the organizer as to how to handle it - I think everyone here shares the idea of wanting the projects to be successful, so if there are problems the group seems willing & able to help out with them - Personally, I think that every one creating a project here should create it as a FB " Event " - This allows to keep the communication about the project centralized - Although there may be posts about projects here, it would be a good way to keep the most pertinant information about the events front & center on the event itself - But the thing is, others might not see it that way.

Volker Störtebeker: One supplement from the Bandcampwebmaster: When I get all the tracks to be placed on Internet I rely on all info, so IF you want url / trackinfo or something else added as info tell the coordinator of a project so that I have all the info I need when uploading the albums.

pszren: One of the things is the invitation. When the group (that is us, EFSPACM people) agrees on a subject/concept (someone usually comes with an idea, or the idea comes during a zoom meeting or during individual conversations), it is best to write an understandable inviatation. With technical details (wav format, wetransfer, but also to give name/title/link when sending a submission), general information about the deadline and what the results will be and "other things" (that a cover art can be included, some inspirations perhaps). Often these tiny problems (no title, not writing to which project the file is supposed to go - when there are two or more projects organized at the same time) cause stress. So it's important to write the invitation well, but also to read it carefully.

If you have more thoughts, questions, or an idea and will to organize an EFSPACM projest, please let us all know on facebook!