JuliaGraphs / JuliaGraphs/MetaGraphsNext.jl

Package name

Open
#58 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
Julia
Stars
93
Forks
24
PR merge metrics
No merged PRs in 30d

Description

It seems that there are discussions about changing the name of the package and I would like to collect future discussion in one place. So, please feel free to post your opinion here !

Following some quotes (from https://github.com/UniStuttgart-IKR/AttributeGraphs.jl/issues/4) to get the conversation started:

@filchristou

I generally do think that that the name "MetaGraphsNext" could be better for a library that ambitions to lead the MetaGraphs regime in julia. However, I would be more concerned on building the infastructure for this rather the naming right now :P
Changing the name could be a 1.0.0 change.

@gdalle

I think we discussed it on Slack briefly but of course Slack has since swallowed it. It's not a pressing matter by any stretch, my thought process was that graph beginners might be scared to use something that's called "MetaGraphsNext" for two reasons:
1. What is "Meta" exactly? It's the data but how would they know
2. The "Next" prefix is useless for anyone unfamiliar with the package history, and may make it seem more complex

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading this issue and the linked AttributeGraphs.jl issue #4, including the quoted discussion about the package name. There are no files or tests identified; done would require agreement on a new name and the scope of any resulting change.

Written by the indexing model from the issue text.

Assessment

Tech stack
julia
Domain
developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.