somesy config harvesting with hermes

[mustafasoylu]

• Discover data from existing files such as pyproject.toml, CITATION.cff
• create .somesy.toml file from this data
• .somesyrc support (in the home directory)

[apirogov]

As discussed yesterday, might be worth taking a look at https://project.software-metadata.pub/# and see if their "harvesting" part would be of use to scrape the metadata together for somesy init.

[apirogov]

@mustafasoylu

I did not check how it currently looks like in the feature branch, but I don't like the way init command works on the main branch right now. What I think it should be doing:

1. Somesy input location

• Check which supported input files exist
• Ask where to put the somesy config and metadata (somesy.toml or pyproject.toml or whatever is supported)

2. Ask if the user wants to import project metadata (from pyproject.toml or other supported input)

• if yes, extract into a SomesyConfig object (could use pyproject_parser that codemetapy also uses),
• otherwise create "default dummy project metadata" (at least for mandatory fields, possibly also optional dummy data to show what somesy supports)

3. dump extracted or default metadata to desired target, including the default values for CLI config fields
4. Tell the user to check the generated config and fine-tune to their needs

[mustafasoylu]

create the somesy.toml file using hermes harvesters.