ruphy
commented
5 years ago Hi @themightychris !
I think I see where this comes and I am thinking it is a valid usecase, but since we want to try to avoid to add new keys as much as possible... I am trying to see whether your usecase could be fit in one of the existing keys.
Have you considered legal/mainCopyrightOwner ? It supports English sentences and could contain your generic name (as in "The NY Brigade and its components"). Note that it does not need to be terribly precise as the AUTHORS file is the one (with the individual files) which contains the precise copyright claims. It was created to more-or-less support your usecase
Another good alternative could be to list a maintainer contact and fill in their affiliation with the brigade name. What do you think about it?
In general, I am trying hard to avoid adding custom fields as I fear that will open a can of worms in terms of small extensions for tracking very different things, and it may lead to severely complicating the format down the line, but let's keep talking.
themightychris
If publiccode.yml were used to document civic tech projects produced in affiliation with local volunteer groups (e.g. Code for America / Code for All brigades) we'd like to document the name of which group within publiccode.yml
The local group is not always the repo owner and not always the copyright owner, nor does it make sense to use a country-specific extension
What approaches to adding this information could be faithful to the format? Essentially we're trying to describe what organization facilitates/moderates/houses a project. This might be the same thing as when a project joins an org like OSI/CNCF. I can't think of a generic term that covers all these cases. Maybe they are different, since volunteer groups don't consolidate copyright ownership like the foundations do
If there's not a standard field to add for this, then the question might change to how do you add extensions that are program-specific rather than country-specific