eiffel-community organization on GitHub and landing page

[Daniel Ståhl]

Hi all,

One of the conclusions at Eiffel Summit before Christmas was that it would be useful with a dedicated organization that can gather all the various parts of Eiffel under one roof, as it is not exclusively an Ericsson initiative. Also, some homogeneity in look and feel and a landing page to help newcomers understand what it is and what it might mean to them would be useful.

Professional assistance in building that online presence would be neat, but I haven't been successful in securing that (yet). In the meantime, I think something is better than nothing, so I started working on this myself.

There is now an eiffel-community organization on GitHub: github.com/eiffel-community
The idea is that every component has its own team of maintainers, rather than a single large team of people who are members of the Ericsson organization. In other words, anyone can be a maintainer, and there can be different maintainers for different components.
This organization also has a web page at https://eiffel-community.github.io/

Next steps would be to begin migrating repositories into the eiffel-community organization, setting up teams of maintainers for them, and making sure they reach a certain standard have a similar look and feel. For instance, they should all have (hopefully similar) contribution guidelines, maintainers mailing lists and so forth. Before I do that I wanted to show what exists so far and get your thoughts on this.

Best regards,
Daniel

[Ola Leifler]

Hi,

I feel this is a great practical step to help contributions from the Eiffel community. Right now, our respositories are distributed in many places which makes collaboration unnecessarily complex.

How about creating new projects in eiffel-community, is that up to you? I’m thinking about persistence in particular that needs to be up there as Azeem is making progress on that project.

/Ola

--
You received this message because you are subscribed to the Google Groups "Eiffel Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eiffel-communi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/eiffel-community/6241be15-8cb4-45b6-9504-bd7fbca6b523%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Daniel Ståhl]

Yup, I'm admin of the organization. So I can create a repository and a maintainer team. Before I start spawning repositories left and right I think I'll make a template repo with some basic hygiene requirements, though. I'm think that every eiffel-community repo should:

• Have a maintainers team (which may be only one person)
  
• Have a maintainers mailing list
• Have contribution guidelines
• Have a code of conduct
• Have PR and Issue templates
• Have a license

There's probably more that could be added to that list, but that's from the top of my head.

[Azeem Ahmad (PhD candidatem LiU)]

Hello Daniel,

This will really help in organizing central/common contribution and effort for/of eiffel community. I am sure, you are aware that many consultant such as Praqma AB, in collaboration with Grundfors, have created some proof-of-concepts. Do you plan to bring them too on this page? I am planning to write a wrapper for neo4j that wrap eiffel events into neo4j specific format (i.e. nodes and relationship) for eiffel persistence as a pilot study, but it can be useful for those, who wants to use ne04j as a persistence solution (of course, we are still investigating the best persistence option), can you please create a page for this repository too?

regards
Azeem

[Daniel Ståhl]

The way I see it anyone is potentially welcome, but we need to have an up-front conversation about project maturity and commitments first. I'm thinking that we can have two types of repositories in eiffel-community on GitHub: one workshop area where basically anything goes, just create a repository to play around and hopefully get people to collaborate with you, and one group of actual identified service implementations.