suggestions for incorporating this in the Graphs.jl ecosystem

[Krastanov]

Hi, @djukic14 ! Thank you for setting up this resources, it is incredibly valuable!

I wanted to post a few suggestions on how we can make this more widely advertised in Graphs.jl and more easily used through Graphs.jl

• Similarly to GraphsOptim.jl and GraphsMatching.jl, have an explicit mention of Graph(s)Coloring.jl in the documentation of Graphs.jl
• Incorporate more of the .github actions to help with management of the repo (e.g. downgrade checks, etc) -- most of them should be just a copy-paste with no need for change of configuration
• Move it to the JuliaGraphs org so that in case you become disinterested in the project in 5 or 10 years, there will be other volunteers to do the more trivial maintenance work.
• Add to the already existing extension in this repository (and to Graphs.jl itself) so that the following can be done:

using Graphs
import Graph(s)Coloring

g = <some_graph>
c = Graphs.color(g, ColoringAlgGreedy())::Coloring
c = Graphs.color(g, ColoringAlgDSATUR())::Coloring
c = Graphs.color(g, etc...)::Coloring

The names above are probably not the best ones, I am just posting it as an example.

It is fine if there will be (hopefully non-breaking) changes to Graphs.jl.

[Krastanov]

I think I updated your org account to have the highest privileges for this repo (no that it is transfered). Let me know if anything is missing.

[cormullion]

You might need to fix the documentation links …

[djukic14]

@cormullion I have updated the documentation links

[djukic14]

@Krastanov Thank you very much for your help! What should I add to the CI/CD pipeline to make GraphsColoring fit better into the organisation?

[Krastanov]

For CI and tests, I would suggest the following:

• downgrade.yml which detects wrong lower compat bounds
• Aqua static analysis tests
• JET static analysis
• running the doctests as part of the test runner (I do not think they are included currently)

I use the https://github.com/QuantumSavory/QuantumClifford.jl/ repository as an example of those, just because I recently cleaned up that type of checks in that repository.

These are probably not very high priority, do not feel like you have to block more exciting or interesting projects on this. You are already putting a lot of volunteer effort in making the ecosystem healthier.