search

plone / meta

Meta issues concerning many/all of the plone repositories.
4 stars 3 forks source link

Tag repositories? #73

Open gforcada opened 1 year ago

gforcada commented 1 year ago

Following zopefoundation organization idea to put a maintained label to repositories where ongoing maintenance support is expected, should we do something similar?

i.e. names totally up to discussion and an example:

This way, given GitHub search UI, we could easily filter for repositories when searching for things, specially given that we have +350 repositories (already excluding archived ones).

stevepiercy commented 1 year ago

I like this idea.

I would suggest adding the label to training and documentation.

We should also document in documentation its purpose and meaning, and how to request it for a repo under the Plone GitHub organization. We don't have a space for that yet, so we would need to create one. It might fit in the new Contributing to Plone structure. Perhaps a new page, "GitHub organization and repository administration" or just "GitHub administration"?

gforcada commented 1 year ago

I like the idea of documenting, yes 🎉 I will try to create a first draft, and then we keep expanding from it 👍🏾

jensens commented 1 year ago

I like the overall idea of tagging. Question is, what helps us? is plone core (and the others) something that helps us with filtering/automation?

gforcada commented 1 year ago

I hope so, at least, we can use it to clearly distinguish, and tell the world what each repository is about with in a quick way.

For example a GSOC student willing to work on Volto stuff, filter for repositories that have the Volto tag ✨

With proper tooling, we might eventually build other interesting things, who knows 🔎

Specially if we want to do a clear split between Classic UI packages, Volto packages and Plone core (what both Volto and Classic depend on), adding this labels can also help navigate, or as I was saying above, with proper tooling we could enforce/lint packages... though that might be easier if the label is rather on the source code... though if we use GitHub REST API it might be the other way around 🤔

mauritsvanrees commented 1 year ago

This should make it easier to for example get a list of all Classic UI packages, and give a new Classic UI team write or admin access to all those.

tooling could be a label, for things like plone.releaser and mr.roboto.

jensens commented 1 year ago

So +1 for all this. But lets first define the labels in detail, with their meaning. Otherwise we would get a jungle of labels, which would lead in the opposite of the initial goal.

gforcada commented 1 year ago

🚂 On the train to Bonn

The list can be:

How does that look like? 🍀

@stevepiercy where would you suggest that to go within the documentation structure? 🤔

stevepiercy commented 1 year ago

@gforcada unless someone has a better idea, https://github.com/plone/meta/issues/73#issuecomment-1500955587 would be the default location and title of the new page. Its filename would be derived from its title.

jensens commented 1 year ago

I would refine:

Additional: