There are no tagged releases in the upstream repository. Would it be wise to build directly from the master branch? If yes, is there a package name convention to follow in this case (like, python-neurocombat-git)?

Is the project active? When is the last commit? Generally, we stick to
releases as much as possible.

And, no, the package name does not change for snapshots, the version and
release does. Search the wiki for "sourceurl", there's a wiki page about it
(i cant remember if its in the guidelines but should be)

Just had a look. Before packaging, you should check if the tool is still valid. So, best to file an issue on the github tracker:

• thanking them for the tool
• informing them that we're considering it for inclusion in NeuroFedora (add link to docs or blog)
• asking if the tool is still being maintained and is OK to use
• and if yes, would it be possible to make a release, also preferably on PyPi

If a python tool is not PyPi, it cannot be installed pip, and that's usually a sign that it isn't ready for end-users.

Sure. Will do the above-said checks. :D

Thanks, please share the github issue here when you've opened it.

(In general, package maintainers aren't just people who take software from upstream and package it. We are active liaisons between upstream and users, so we also help upstream improve their software, sending patches, making suggestions, and poking them about issues when needed. https://fedoraproject.org/wiki/Staying_close_to_upstream_projects is a good page to read)

Here is the GitHub issue.

(The job of a package maintainer sounds more interesting now.. :stuck_out_tongue: )

Project is deprecated, closing.

I have no idea how I allegedly reopened this.