-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discussion: How to make the projects portal customizeable #26
Comments
This is an interesting angle to make it easier to reuse the project and contribute to it. Some other ideas where customizability could be helpful:
|
@spier #26 (comment) all good considerations. |
I'm thinking about how I'd like the experience to be from a developer's perspective reusing the portal.
|
A suggestion for the portability: Rename That way if the sample data gets updated I don't get merge conflicts when I pull from upstream. |
👋 One thing I've done to customize the portal for a few companies is to insert any "Overview metrics" right at the top just above the search bar and filters. This is done through a nightly automation to keep the stats fresh. Example: "424 InnerSource repositories, 10% of all repositories, 21hr average time to first response on Pull requests, Average security score: 90" |
Hi @svrnm, this is an interesting suggestion. I'll discuss it with @Michadelic. @zkoppert , that's an interesting customization, thanks for sharing! |
thanks @dellagustin |
Amazing list of suggestions to customize the portal. Thank you so much for bringing these ideas together and the discussion here in this thread. I will have a look and i am also very open for public contributions on this issue. Maybe we can jointly create a concept and work on it. My two cents for getting it implemented:
We could start with the config.json file and the list of suggestions in this thread and later add the wizard. What do you thing? PS: the overview metrics is also an interesting idea. This would probably done in the crawler at the end and update an entry in the |
Having a configuration to fill out the page details is a great idea! It also helps to find all the things that need to be changed since on the HTML page they are at very different places 👍 A few other suggestions:
|
As mentioned on the the ISC Community Call InnerSource and Discoverability, one of our ideas for the portal is to make it customizeable.
What is the problem?
Currently, the way to reuse the portal is to fork it and modify it, it is not reusable in the sense of being a customizeable dependency that can be reused without modifications.
One of the cons of this approach is that it is harder to keep it up to integrate updates, as there may be conflicts between the changes on the original repo and the forks.
Here are some of the features that could be customizeable:
What is this issue about
I created this issue to collect ideas on how we could make the portal customizeable.
Features we should keep
One of the great features of the portal today is that it can be easily hosted as static files. This make it easy to operate, as it can be hosted for instance on GitHub pages. When making customizeable, we should aim to keep it for simplicity.
The text was updated successfully, but these errors were encountered: